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

Annotations establish the write profile (readOnlyHint=false, destructiveHint=false), and the description usefully adds that the operation is state-changing, requires prior authorization, recursively copies children, and that copies landing in a public target Space are publicly accessible. It does not address name-collision handling or whether the copy is atomic, so it is strong but not complete.

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-loads the when-to-use clause, then behavior, then parameters. The final parameter sentence largely duplicates what the schema already encodes at 100% coverage, which is minor redundancy rather than bloat.

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 state-changing tool with no output schema, the description covers the trigger, the authorization precondition, and the public-visibility consequence — enough to call it correctly. It omits whether new item IDs are returned for follow-up calls, which is the main remaining gap.

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 all four parameters are already documented, and the description only restates which are required versus optional without adding format, ID-sourcing, or null-handling detail. Baseline 3 applies when the schema carries the semantics.

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?

States a specific verb (copy/duplicate/clone), the resource (Space page/document, folder, external link) and the scope (including its children), and places the result precisely (into another Space). This clearly separates 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?

The lead clause gives a clear trigger condition and lists the synonyms a user might say, which aids selection. It stops short of naming the natural alternative (move-space-item) or stating when not to use it, so it is contextual but not exhaustive.

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