Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the mutation risk is known. The description does add genuine value beyond them by disclosing that the previous page tree is saved as a private rollback snapshot first, which tells the agent a recovery path exists. It stops short of noting any permission requirements or what the snapshot covers (single page vs. global).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense sentence plus a short clause about position=-1; nothing is padded and the rollback behaviour is stated before the positioning detail. The trailing fragment is terse but readable, costing only minor polish.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, five-parameter mutation tool with no output schema, the description covers the essential mechanics (reparent/reorder, rollback snapshot). It does not address ordering constraints relative to save_page_data, whether element_id must come from get_page_structure, or what happens on failure, which an agent would need to avoid a bad move.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 20% (only site_id is documented), so the description must compensate; it does explain parent_id's dual role (root vs. reparent) and that position=-1 appends. element_id and post_id carry no added meaning, and the interaction between position and parent_id (e.g. index within the new parent) is left implicit.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Moves an Elementor element") plus destination scope ("to the root or into another parent element"), which is enough to distinguish it from create/remove/update siblings. It never names a sibling move tool (wp_move_block, wp_move_widget) to clarify which mover applies, so differentiation is implied rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

Destination semantics imply when to use it — omit parent_id to move to root, supply one to reparent — and "position=-1 appends" tells the agent how to place at the end. There is no explicit when-not guidance, no prerequisites (e.g. requiring an existing saved page tree), and no routing to alternative tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.