duplicate_template

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

The description does not disclose what duplication entails (e.g., whether it copies all properties, generates a new ID, or has side effects). Annotations are minimal (readOnlyHint false, destructiveHint false) and don't compensate.

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?

Single sentence, direct and clear. Could add more detail without becoming verbose, but remains efficient.

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?

No output schema and no description of return value (e.g., does it return the new template object?). For a simple tool, the description could be more complete regarding the result and edge cases (e.g., behavior when name is omitted).

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% for both parameters, so the description adds no additional meaning beyond what is already in the schema. Baseline score of 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?

The description clearly states the action 'duplicate' and the resource 'template', distinguishing it from create, update, delete, and other template tools.

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?

No guidance on when to use this tool versus creating a template from scratch or updating an existing one. Prerequisites (e.g., existence of the source template) are not mentioned.

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