delete-experiment-tag

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

The description implies a destructive operation (deletion), but does not disclose behavior such as idempotency, error handling if the tag doesn't exist, or any side effects. With no annotations, the description carries full burden but remains minimal.

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, efficient sentence of 6 words with no extraneous information. It is appropriately brief for a simple deletion tool, though the structure is flat.

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 tool with only two simple parameters and no output schema, the description conveys the core functionality. However, it lacks context about error states (e.g., non-existent tag) or the relationship to sibling tag tools, leaving minor gaps.

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 covers 100% of parameter descriptions ('Experiment ID' and 'Tag key to delete'). The tool description adds no additional meaning beyond what the schema already provides, meeting the baseline expectation.

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') and resource ('a tag from an experiment'), making the tool's purpose evident. However, it does not differentiate from sibling tools that also delete tags from other entities (e.g., delete-run-tag), limiting its clarity in 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 is provided on when to use this tool versus alternatives like delete-run-tag or set-experiment-tag. There are no usage hints, exclusions, or prerequisites, leaving the agent to infer from context alone.

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