copy_tag

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

With no annotations provided, the description carries full burden. It states the tool creates a new tag but doesn't disclose behavioral traits like whether it overwrites existing tags, requires specific permissions, handles errors, or affects system state beyond the tag duplication. The phrase 'with all tasks and metadata' adds some context but is insufficient for a mutation tool.

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, efficient sentence that front-loads the core action ('copy an existing tag') and specifies the outcome ('create a new tag with all tasks and metadata'). There is no wasted verbiage or redundant information.

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 mutation tool with 5 parameters, no annotations, and no output schema, the description is incomplete. It lacks information about return values, error conditions, side effects, and how it integrates with sibling tools. The high schema coverage helps, but the description doesn't compensate for missing behavioral context.

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%, providing clear documentation for all 5 parameters. The description adds minimal value beyond the schema, mentioning 'existing tag' (implied by sourceName) and 'new tag' (implied by targetName), but doesn't explain parameter interactions or provide additional context like format examples.

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 ('copy') and resource ('existing tag'), specifying that it creates a new tag with all tasks and metadata. It distinguishes from siblings like 'add_tag' (which likely creates from scratch) and 'rename_tag' (which modifies rather than duplicates), though it doesn't explicitly name these alternatives.

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 explicit guidance on when to use this tool versus alternatives like 'add_tag' or 'rename_tag'. The description implies usage for duplicating tags with their content, but lacks context about prerequisites, constraints, or when other tools might be more appropriate.

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