delete-run-tag

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

The description 'Delete' aligns with the destructiveHint=true annotation, but adds no extra behavioral context beyond what the annotations already convey. It does not mention side effects, reversibility, permission requirements, or the implication of openWorldHint=true.

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 sentence, which is concise. However, for a destructive operation, it could benefit from additional structured information such as expected outcomes or warnings. It is not overly verbose, but the brevity reduces 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 low complexity (2 simple parameters, no output schema), the description is minimally adequate but incomplete. It does not specify the return value, error conditions, or the tag key's format. The openWorldHint=true suggests dynamic data, but the description does not address this.

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?

The input schema has 0% description coverage, and the tool description adds no meaning to the parameters 'runId' and 'key'. The description fails to explain that 'key' likely represents the tag key to delete, leaving the agent without essential semantic context.

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 run' clearly states the verb ('Delete') and resource ('tag from a run'), distinguishing it from sibling tools like 'delete-run' or 'delete-experiment-tag'. However, it does not explicitly differentiate from other tag deletion tools, such as 'delete-experiment-tag'.

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 usage guidelines are provided. The description does not specify when to use this tool versus alternatives like 'set-run-tag' or other delete tools. There is no mention of prerequisites or contexts where the tool is applicable.

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