move_page

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

No annotations are provided, so the description carries full burden. It discloses that the PATCH endpoint silently ignores parent changes, returns HTTP 200 but does not move the page, and that this tool is preserved only to return a clear error message. Complete behavioral disclosure.

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?

The description is front-loaded with 'NOT SUPPORTED', which immediately conveys the key message. It is concise but includes necessary details about alternatives. Slightly more verbose than ideal, but well-structured.

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?

Given that the tool is a placeholder for an unsupported action, the description is fully complete: it explains the API behavior, the fact that the tool exists only for error messaging, and provides two alternatives with their caveats (destructive nature, media degradation, recommendation for nested pages). No gaps.

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 description coverage is 0%, and the description does not explain the parameters (page_id, new_parent_id, parent_type) beyond what the schema provides. Since the tool is a no-op, parameter details are less critical, but the description still does not add meaning for them.

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 that the tool does NOT support moving a page, explaining the API limitation and what it actually does (returns an error message). This is a specific verb-resource-purpose and distinguishes from sibling tools like copy_page_to_parent.

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?

The description explicitly says 'NOT SUPPORTED' and provides clear when-not-to-use guidance. It also gives two working alternatives (copy_page_to_parent and manual drag) with details on their trade-offs, so the agent knows exactly what to do instead.

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