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

Annotations already convey readOnlyHint=false and destructiveHint=false, so the safety profile is covered. The description adds one useful behavioral detail—that widgets are duplicated along with the asset—but does not mention other side effects, whether the source remains unchanged, or any permission requirements. This is moderate additional context beyond the annotations.

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, tightly worded sentence that front-loads the core action and scope. Every word earns its place, and there is no filler or repetition of schema details.

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?

The tool is simple: 4 flat parameters, fully described in the schema, with an output schema present. The description covers the essential operation and widget behavior. It would be fully complete if it noted that the source asset is unchanged, but that is arguably covered by the non-destructive annotation. Still, a small gap remains.

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?

The input schema has 100% description coverage, with each parameter (id, name, tags, description) clearly explained. The tool description only reiterates the 'under a new name' idea that maps to the name parameterholed, adding no new parameter-level insight. Baseline 3 is appropriate given the schema carries the param 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?

The description states a clear action ('Duplicate'), a specific resource ('asset'), and a scope ('and its widgets') plus the target outcome ('under a new name'). It is specific enough to distinguish from unrelated tools, but it does not explicitly differentiate from sibling duplicate_* tools like duplicate_report or duplicate_goal, so it stops short of a 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 gives no guidance about when to use this tool versus the other duplicate_* siblings, nor any conditions, prerequisites, or exclusions. The only usage signal is the word 'asset' in the description, which is implied but not explicitly contrasted with alternatives.

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