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

Adds real context beyond the annotations: what gets copied, that the output is a *draft* rather than a published demo, and the required scopes demos:read/demos:write. It implicitly explains the non-idempotent hint (each call makes another copy) but does not state the source is left untouched or what the response contains.

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?

Two sentences of behavior plus a permission line; the core copy semantics are front-loaded and nothing is padding. The name_format detail is compactly embedded rather than belabored.

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 single-input, non-destructive duplicate operation with full annotation coverage, the description covers inputs, permissions, and resulting state. The only gap is not saying what the call returns (e.g. the new demo's id), which matters because there is no 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?

Only one parameter and the schema already documents it fully with a pattern and an example value sourced from list_demos. The description adds no further meaning about demoId, so the baseline 3 applies.

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 (copies) and resource (a demo) and enumerates exactly what is carried over — screens, content, settings, translations — plus the resulting artifact being a new draft. This clearly distinguishes it from update_demo, translate_demo, or stitch_demo.

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?

"Useful for a variant per audience" gives a motivating scenario, which is more than nothing, but there are no explicit when-to-use/when-not conditions and no routing to alternatives such as translate_demo or stitch_demo for related-but-different jobs.

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