Copy Page

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

With only destructiveHint=true available in annotations, the description adds meaningful implementation detail: Server/DC fetches the body and creates the page manually, and attachments are not copied in that path. This tells the agent what to expect beyond the annotation. The description does not contradict the destructiveHint.

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 short sentences, first is front-loaded with the core action; the subsequent sentences layer platform caveats without waste. 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?

The main platform-specific behavior and attachment limitation are covered, and the output schema plus 100% parameter documentation handle return values and parameter details. It does not address alternatives or original-page side effects, but those are not required for a correct call.

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 value by explaining why copy_attachments is only supported on Confluence Cloud ('attachments are not copied in the Server/DC path') and that the page body is fetched and recreated, clarifying the mechanism behind destination parameters.

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 opens with a clear verb-resource statement: 'Copy a Confluence page to a new location.' The word 'copy' plus 'new location' distinguishes it from sibling create/move/delete operations, and later 'new page is created manually' reinforces that the original is being duplicated rather than moved.

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 provides platform context (Cloud native endpoint vs Server/DC manual fetch-and-create) but no explicit when-to-use guidance or alternatives. The intended use is implied by the title and first sentence, but there is no statement distinguishing this from move_page or create_page.

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