delete-logged-model-tag

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

With no annotations, the description should disclose behavioral traits like permanent deletion, required permissions, or side effects. The description is minimal and does not add any behavioral context beyond the action itself.

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?

Extremely concise single sentence with no wasted words. However, it could include more context without becoming verbose; current conciseness borders on under-informativeness.

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 the simplicity (2 params, no output schema) and sibling tools, the description lacks context on prerequisites, error states, or effects. It does not help an agent distinguish usage from similar tag-deletion tools.

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 50%: 'key' has a description, but 'modelId' lacks one. The description adds no additional meaning beyond the schema; it does not clarify what 'modelId' refers to or format requirements.

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 'Delete a tag from a LoggedModel' clearly states a specific verb (delete) and resource (tag from LoggedModel). It distinguishes from siblings like 'delete-logged-model' (deletes entire model) and 'delete-run-tag' (different context).

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 alternatives (e.g., 'delete-model-version-tag', 'delete-run-tag'). Usage is implied by name and description, but no explicit when-to-use or when-not-to-use context.

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