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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is partly covered. However, the description adds no behavioral context: it does not explain what makes duplication destructive, whether the original remains, whether existing placement is overwritten, or what happens to session content. That gap is notable for a destructive mutation.

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?

The description is a single front-loaded sentence with no filler. It is appropriately concise, though its brevity leaves behavioral gaps that are scored elsewhere. The structure itself is clean.

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 destructive, non-idempotent mutation with nested placement options and no output schema, one sentence is not enough. The schema and annotations cover parameters and safety flags, but the description never clarifies the result of duplication, overwrite behavior, or session/auth constraints. It is materially under-described for this complexity.

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 schema already documents subject, sessionToken, requestId, and the nested options object. The description only refers vaguely to "existing placement options" and does not add syntax, aliases, or selection rules beyond the schema. Baseline 3 is appropriate.

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 states a specific verb and resource: "Duplicate the specified text or image." It also scopes the operation to the element's print area and existing placement options, which distinguishes it from sibling add_text/add_image tools that create new content. It stops short of explicitly naming alternatives, so a 4 rather than 5.

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 description explains what the tool does but not when to choose it over add_text, add_image, or change_design. There are no exclusions, prerequisites, or alternative-selection guidance. At best, duplication is implied by the verb; no real usage guidance is provided.

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