Move page

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

Adds behavioral context beyond annotations: permission requirements and parameter mutual exclusivity (make_root vs parent_id). Annotations already indicate idempotent and non-destructive, and the description does not contradict.

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?

Three sentences, each serving a distinct purpose: operations, permissions, constraints. No redundant or extraneous text.

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?

With output schema present, the description covers all necessary aspects: actions, constraints, and permissions. No critical gaps for an idempotent, non-destructive move operation.

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 100%, and the description adds value by grouping parameters by operation and clarifying constraint ('mutually exclusive with parent_id'). This reduces ambiguity about which parameters to combine.

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?

The description clearly states the action (move a page) and specifies the four operations (reparent, detach, reorder, relocate). It distinguishes this tool from sibling tools like update_page and patch_page by focusing on structural movement rather than property updates.

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?

Provides explicit permission requirements ('Editor+ in both source and target space') and mandatory parameter condition ('Provide at least one of...'). No explicit comparison with alternatives, but the constraints are sufficiently clear for correct usage.

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