confluence_move

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

With no annotations, the description carries full burden. It discloses the returned YAML metadata (id, title, parent_id, ancestors), the three position behaviors, and the same-space limitation. Does not mention permission requirements or side effects on page content/attachments, but covers key behavioral aspects.

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?

Three sentences, no wasted words. Front-loaded with action, followed by position semantics, constraint, and return format. Every sentence earns its place.

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 no output schema, description adequately specifies return format. Parameters are fully described with added context. Constraints are clear. The tool is well-situated among sibling tools with a distinct identity.

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 coverage is 100%, so baseline is 3. Description adds value by clarifying position defaults ('append'), explaining each position meaning in context, and elaborating target_id's role relative to position. This exceeds schema 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?

Clearly states 'Move or reparent a Confluence page within its current space.' Uses specific verb and resource. Distinguishes from sibling tools like confluence_create, confluence_delete, etc., by focusing solely on moving/reparenting.

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?

Provides explicit constraint 'Same-space only — cross-space moves are not supported,' helping the agent avoid misuse. Explains position options. Lacks explicit comparison to alternative tools for cross-space scenarios, but the constraint effectively guides when not to use.

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