Delete Tag

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

With no annotations provided, the description carries the full burden. It discloses the permanence of the deletion and its cascade to all monitors using the tag, which is key behavioral context. It does not mention permissions or other limitations, but the essential side effects are clear.

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?

Two succinct sentences. The first covers action and consequence; the second provides a useful tip. No filler, each sentence earns its place.

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 one-parameter delete tool, the description explains the permanent nature, the impact on monitors, and how to obtain the required ID. No output schema is expected for a delete, and the description fully prepares the agent for invocation.

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 defines tagID as the ID of the tag to delete (coverage 100%). The description adds a practical hint on sourcing the tag ID via listTags, enhancing the schema without redundancy.

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 tool deletes a tag permanently and specifies the cascading effect on monitors. It uses a specific verb ('deletes') and resource ('tag'), and distinguishes from siblings like addTag or listTags by focusing on deletion and its impact.

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 a concrete usage hint ('Use listTags to find the tag ID'), which guides the user on a prerequisite step. It does not explicitly mention when not to use it or alternatives, but for a simple delete operation this is adequate.

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