Delete Tag

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

The description discloses two important behavioral traits: the operation is permanent ('Permanently deletes') and it has a side effect on associated monitors ('removed from all monitors that use it'). Since no annotations are provided, this information is essential for the agent to understand the consequences.

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 two short sentences, each serving a clear purpose: stating the action and providing the prerequisite. There is no redundant information.

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 single-parameter delete tool, the description covers the core action, the irreversible/cascading nature, and how to find the required ID. An output schema exists, so return values are not the description's responsibility. This is complete for the tool's complexity.

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 schema fully documents the tagID parameter with 100% coverage, so a baseline score of 3 applies. The description adds the practical hint 'Use listTags to find the tag ID', which tells the agent how to obtain the required parameter value.

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 ('Permanently deletes') and the resource ('a tag'), and distinguishes it from sibling delete tools by noting the tag-specific side effect ('removed from all monitors that use it'). This makes the tool's purpose unambiguous.

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?

It provides the prerequisite step 'Use listTags to find the tag ID' and clarifies the cascading effect on monitors, giving context for when to use it. However, it does not explicitly state when not to use it or alternatives, though for a delete operation this is less critical.

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