Move Page

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

Beyond the annotations, the description discloses an important side effect: 'Child pages move with it.' It also explains ordering behavior (end by default, start with first=true, or after after_page_id). It does not cover permissions or failure conditions such as attempting to move a page under its own descendant.

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 two tightly written sentences with no filler. It front-loads the scope and destination behavior before adding the child-page side effect.

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 same-space move operation with full schema coverage, annotations, and an output schema, the description covers the key calling context: destination modes, ordering, and child-page movement. Remaining gaps are around error conditions and explicit sibling routing, but no essential invocation detail is missing.

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?

The schema already documents all four parameters at 100% coverage, but the description adds relational meaning: an empty parent_page_id means top level, first=true places the page at the start, after_page_id places it right after a specific page, and the default destination is the end of the level. It does not explicitly state whether first and after_page_id are mutually exclusive.

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 and resource: 'Move a page to another place in the same space.' It immediately clarifies the destination options (parent_page_id or top level) and implicitly distinguishes this from the cross-space sibling move_page_to_space by emphasizing 'same 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 clear context for when to use this tool: moving within the same space, either under a parent or to top level. It also explains how to choose placement using first=true or after_page_id, but it does not explicitly name move_page_to_space as the alternative for cross-space moves.

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