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

Annotations provide readOnlyHint=false and destructiveHint=false, so the agent knows it's a write operation but not destructive. The description adds that it duplicates widgets, which is useful beyond annotations. It doesn't disclose what exactly gets duplicated (e.g., tags, description defaults) or implications like permissions, but that's partially in the schema. It doesn't contradict annotations, so score is moderate.

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 one short sentence, front-loaded with the verb and resource. It's efficient but lacks any additional context that would make it more useful. It earns a neutral 3 because it's concise but doesn't add much value beyond the name.

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 duplication tool with an output schema and high schema coverage, the description is reasonably complete. The key point about duplicating widgets is included. However, it doesn't clarify behavior like potential name conflicts or how it interacts with the source asset, but that may be covered by the output schema. Overall, it's adequate for the tool's 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 coverage is 100%, so the schema already documents all parameters. The description adds minimal extra meaning: it repeats the operation and mentions widgets, but doesn't explain the semantics of 'new name' or how defaults work for tags/description. Since schema has high coverage, baseline is 3, and the description doesn't push beyond that.

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 the verb 'Duplicate' and the resource 'asset' with a parenthetical about including widgets, which is clear. It doesn't explicitly distinguish from sibling duplicate_* tools (e.g., duplicate_report, duplicate_goal), but the subject 'asset' in the description and title is specific enough. The plural 'widgets' adds useful scope.

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?

It doesn't state when to use this tool versus alternatives, but the resource is clearly different from other duplicate tools, so an agent can infer usage. The inclusion of '(and its widgets)' implies the full asset duplication scope, but there's no explicit mention of alternatives or when not to use. The tool name and siblings make the choice relatively straightforward.

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