Sure, but examples are examples, not the absolute outer bounds. The spell doesn't say anything like "if the DM determines the command is more powerful than the examples, the spell ends".So, the examples of what Command does, as in the bulk of the text of the spell, appears nowhere in your PHB? You should get that checked out. My PHB certainly includes them, as do every PHB since 1e.
The definition of the spell doesn't say "the target can only move toward or away from the caster or just not move at all". Unless you interpret the potential for falling as "directly harmful to it" (and unless there are circumstances that make falling particularly dangerous or likely, I wouldn't), this isn't an abuse of the definition of the spell.Climb - requires a skill check which may fail, causing the target to fall and take damage. It's entirely possible that the target literally is not capable of climbing whatever it is that you want it to climb. Also, it's vague. Up or down? You are abusing the definition of the spell where the examples are all move towards the caster or move away from the caster or just not move at all.
The spell doesn't say "you can cause the target to drop something at their feet but that's it". Drop is just an example, not a limit.Throw - again, beyond the scope of the spell. The spell can cause you to drop something at your feet, but, that's it. Now you are making the NPC actually take an action, again, not permitted by the spell, and potentially attacking someone - after all, I can throw my spear at someone and attack, again expressly not permitted by the spell.
It also doesn't say "you can't make the NPC take an action". Attacking is not expressly prohibited. You might argue that it is implicitly prohibited, since if it were allowed, they would probably have given that as an example. That's not an unreasonable position, but nothing in the text of the spell says
But on the other hand commands like "attack" aren't usually a very good idea, since you can't tell them whom to attack, so maybe they were just trying to list a few that are more generally useful.
It's fine if you want to interpret it as not being able to force the target to take an action, but arguing that people who don't interpret it that way are "rewriting" the spell is not correct.
It's only clearly more powerful than "Drop" if you assume the direct object has to be "your weapon" and the indirect object has to be "a PC". But you can't command them to give a PC their weapon, only "Give".Give - Same as throw really. Give what? My opinion? My attention? The spell permits me to cause someone to drop what they are holding, but, handing it to someone else? Fantastic disarming spell - after all now all I have to do is get the NPC to give their weapon to another PC and we're golden. Clearly more powerful than "Drop".
In my interpretation, a low intelligence enemy would probably give something already in their hands to the nearest creature, but if they're a bit clever, they'll choose to give something unimportant or give something to their friend. So it's more circumstantial than drop.