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

Annotations are all false with no hints about effects, so the description carries the burden. It clearly states that the tool creates a new design, leaves the source unchanged, and returns the new design_id. This meaningfully explains the behavioral outcome beyond the schema.

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 concise and well-structured: the core action is in the first line, usage scenarios follow, and the key side-effect/result is stated last. Every sentence earns its place with no filler.

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 low-complexity tool with a fully documented schema and no output schema, the description covers what the tool does, when to use it, what it creates, the source immutability, and the returned design_id. Nothing essential is missing for correct invocation.

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 design_id and page_numbers thoroughly. The description adds a small hint by mentioning 'copy selected pages', but does not go beyond the schema's explicit parameter documentation.

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 uses a specific verb ('Duplicate') and resource ('existing Canva design'), and explains the page-selection variation. It distinguishes itself from siblings by explicitly stating it is not for combining pages from more than one design, setting it apart from merge-designs.

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 explicitly lists when to use the tool: making a separate working copy, cloning, forking, backing up, or preserving the original. It also gives clear exclusion criteria: single source design only and not for combining pages from multiple designs.

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