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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is partly given. The description adds genuinely new context beyond that: authorization is required, changes are state-changing, children are copied along with the item, and copies landing in a public target Space are publicly accessible. It could still note that source items are left intact, but the added disclosure is substantive.

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?

A tight three-sentence block: trigger first, then behavioral implications, then the parameter summary. Every sentence carries information, though the trailing parameter list is somewhat redundant with the schema.

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 4-parameter mutation tool with no output schema, the description covers the trigger, the mutation semantics, the authorization requirement, the public-visibility consequence, and the parameter set. The main remaining gap is behavior on name collisions or partial-copy failure, which is minor.

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 with their roles (source, target, parent/root). The description only restates the required/optional split and adds no syntax or constraint details beyond the schema, which is the expected baseline at full coverage.

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 gives a specific verb (copy/duplicate/clone) plus the resource (Space page/document, folder, external link, and its children) and the destination (another Space). It is clearly distinguishable from siblings like move-space-item, create-space-item, and update-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?

"Use this when the user wants to copy, duplicate, or clone..." gives an explicit trigger condition, which is strong. It stops short of naming alternatives (e.g., move-space-item for relocating instead of duplicating), so the routing guidance is clear but not fully comparative.

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