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

Clearly discloses that this is state-changing, creates copies in the target Space, and includes children. This adds context beyond the annotation values and does not contradict readOnlyHint=false or destructiveHint=false.

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?

Front-loaded with a clear usage trigger and kept to two sentences, but the 'Requires...' sentence duplicates schema information and the synonym chain 'copy, duplicate, clone' is slightly redundant.

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?

Covers what is copied, that children are included, where the copy is created, and the side effect. Missing details like naming conflicts or permission requirements are not critical given the absence of an output schema.

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% and each parameter is already described in the input schema. The free-text description does not add meaningful per-parameter semantics beyond repeating the required 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?

Names the exact operation (copy/duplicate/clone), the resource types (Space page/document, folder, external link), and the destination (another Space), which distinguishes it from siblings like move-space-item and create-space-item.

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?

Explicitly says 'Use this when the user wants to copy...' and lists required parameters, but it does not explicitly mention alternatives such as move-space-item or create-space-item for non-copy actions.

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