Update Tag or Task

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

With annotations already declaring destructive and idempotent hints, the description adds minimal behavioral context. It doesn't mention the 'confirm' parameter or explain what 'partial' means in terms of field updates.

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, front-loaded sentence with no waste. However, it is under-specified and lacks structured detail that would help the agent.

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 has 5 parameters with a nested spec object and no output schema, but the description is one sentence. No mention of confirmation requirements, parameter effects, or expected behavior, leaving the agent to infer from names.

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 0%, and the description offers no parameter information. The 'spec' object, 'confirm', and 'global_tag' semantics are entirely unexplained.

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 uses a clear verb ('update') and resource ('tag definition'), with scope ('local or global') that distinguishes it from create/delete/apply siblings. However, it omits the 'task' aspect from the title, making it slightly less precise.

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 provides no guidance on when to use this tool versus alternatives like create or delete. It only states the action, with no context or exclusions.

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