delete-model-version-tag

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

No annotations provided, so description must disclose behavior. Only states 'Delete a tag' without mentioning side effects, permission requirements, error handling (e.g., missing tag/version), or idempotency. Insufficient for a destructive operation.

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 is extremely concise, but the brevity sacrifices informational completeness for a tool with no other documentation. Could add a second sentence for context without losing conciseness.

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 or annotations; description does not cover what happens on success/failure, missing parameters, or side effects. For a tool with three required parameters, the description is incomplete for safe agent use.

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 has 0% description coverage and three parameters (name, version, key) with no documentation. Description adds limited meaning (delete action) but does not explain each parameter's role or format. Falls short given the schema gaps.

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?

Description clearly states verb (Delete) and resource (tag from a model version), and distinguishes from sibling tools like set-model-version-tag (add/update) and delete-model-version (delete entire version).

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?

Description provides no explicit when-to-use or when-not-to-use guidance. The action is clear from the name but lacks context on prerequisites or alternatives, making it minimally adequate.

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