delete-model-version-tag

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

Annotations already indicate the tool is destructive (destructiveHint: true). The description adds only that it deletes a tag, but fails to disclose behavioral details such as idempotency, error handling if tag doesn't exist, or impact on related data.

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 clear sentence with no fluff. However, it is almost too concise, omitting potentially valuable 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?

Given no output schema, the description does not specify what happens after deletion (e.g., returns success, confirmation, or nothing). It also lacks context about when to use this tool over siblings like 'delete-model-version' or 'set-model-version-tag', making it incomplete for an agent.

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 does not explain the parameters (name, version, key). While 'delete a tag from a model version' loosely maps to these, it does not clarify which parameter corresponds to what, leaving ambiguity.

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 (delete), resource (tag), and context (from a model version). It is specific and distinguishes from sibling tools like 'set-model-version-tag' (which adds/updates) and 'delete-model-version' (which deletes the version itself).

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 does not explicitly state when to use this tool versus alternatives, nor does it mention prerequisites (e.g., tag must exist, version must exist). Usage is implied by the action, but no exclusions or guidance are provided.

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