move_page

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

Annotations already establish that this is a mutating but non-destructive operation. The description adds a useful behavioral detail: position is computed by default unless an explicit 5-12 character key is passed. It doesn't disclose side effects, permissions, or what happens to child pages, but the annotation coverage lowers the burden.

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?

Two sentences with no fluff. The main action and destination are front-loaded, and the position nuance is stated in the second sentence without repeating schema details.

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 five-parameter tool with full schema coverage and no output schema, the description gives the essential high-level behavior and position semantics. It doesn't explicitly mention after_page_id or compare against move_page_to_space, but the schema covers the remaining parameter semantics well enough for correct invocation.

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 100%, so the baseline is 3. The description adds genuine semantic value by explaining that position is computed unless an explicit fractional-index key is supplied, and by framing parent_page_id/root as the two destination modes.

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 states a specific verb ('Move') and resource ('a page') and clearly distinguishes the two main destinations: a new parent or the space root. This differentiates it from the sibling move_page_to_space, which implies moving to a different space.

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?

It gives implied usage context: the tool is for reparenting a page or moving it to the space root, and position is computed unless an explicit key is provided. However, it never explicitly says when to choose this over move_page_to_space or other siblings, so the guidance is partial.

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