move_page

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

With no annotations, the description carries full burden. It discloses the leaf promotion behavior but omits other potential side effects, such as what happens to the old parent or error handling (e.g., circular moves).

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 concise sentences front-loading the main action with a key behavioral detail. Every sentence adds value with no unnecessary words.

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 3-param tool with no output schema, the description covers the core operation and an edge case (leaf promotion). However, it lacks details on constraints (e.g., cannot move to descendant), return values, or failure conditions.

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%, so the description must compensate. It adds context that the move is 'within the same collective' and explains the behavior of newParentPageId (leaf promotion), but does not individually describe collectiveId or pageId beyond their names.

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), resource (page), and specifies it's within the same collective, distinguishing it from sibling tools like copy_page or rename_page. It also notes a special case (leaf promotion).

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 explains what the tool does and a behavioral nuance (leaf promotion) but does not explicitly guide when to use it versus alternatives like copy_page, or when not to use it (e.g., cross-collective moves).

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