Move Page

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

The description only restates the core action and adds no behavioral context beyond the destructiveHint annotation. It does not mention side effects like removing the page from its old parent, impact on child pages, or permission requirements. It is consistent with the annotation, but adds no extra transparency.

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 a single, front-loaded sentence of 10 words with no redundancy. Every word carries meaning, making it optimally concise.

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 the tool's simplicity, complete parameter schema, output schema, and destructiveHint annotation, the description sufficiently conveys the core function for invocation. However, it lacks guidance on when to use it vs. alternatives, which slightly reduces completeness.

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 schema already documents all parameters. The description only echoes the destination concept ('new parent or space') and adds no additional meaning beyond the parameter descriptions.

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 uses a specific verb ('Move') and resource ('a Confluence page') with a clear destination ('to a new parent or space'). This distinguishes it from sibling tools like copy_page, delete_page, or update_page within the same family.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., copy_page for duplication, or update_page for editing). There are no mentions of prerequisites, exclusions, or context for choosing it.

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