delete-experiment-tag

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

The description simply says 'Delete', which is consistent with annotations (destructiveHint=true). However, it adds no context beyond what annotations already provide, such as idempotency, what happens if tag doesn't exist, or whether deletion is permanent.

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 extremely concise (one short phrase). It is front-loaded with the core action and resource, with no unnecessary words.

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?

For a simple delete operation with two well-described parameters and annotations indicating destructiveness, the description is adequate. However, it lacks details on error states (e.g., tag not found) and return behavior.

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 100% with both parameters described ('Experiment ID', 'Tag key to delete'). The description adds no additional meaning beyond the schema.

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', the resource 'tag', and the scope 'from an experiment'. It is distinct from sibling tools like delete-experiment (deletes whole experiment) or delete-run-tag (deletes run 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?

The description provides no guidance on when to use this tool versus alternatives (e.g., set-experiment-tag for updating). It does not mention prerequisites, error handling, or idempotency.

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