Sprint Planning answers why this Sprint is valuable, what can be Done, and how the chosen work will get done. The whole Scrum Team collaborates. The Product Owner brings an ordered backlog and a proposal for value; the Developers select the work and create the plan.
Recent delivery helps you forecast. Capacity changes matter too: holidays, support duty and leave can reduce what is feasible. Story points are not hours, and scaling velocity by capacity gives a rough planning input, not a guarantee.
The Sprint Goal is one coherent objective. Keep room to adapt the detailed scope as you learn. Developers and the Product Owner may renegotiate scope during the Sprint without endangering that goal. An executive's wish list does not increase the team's capacity.
Capacity supports a forecast; the Sprint Goal provides focus.