delete_tag

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

With no annotations provided, the description carries the burden of disclosing behavioral traits. It explicitly states that subscribers with this tag will not be deleted, which is a key side-effect often associated with delete operations. However, it could add detail on irreversibility or error behavior, so it is not fully transparent but strong for the core concern.

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 with the core action front-loaded and a parenthetical clarification. Every word is functional, with no redundancy or fluff. It is concise yet informative.

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?

This is a simple delete operation with one parameter, and the description addresses the main safety concern (no subscriber deletion). The lack of an output schema means return values don't need explanation. However, it omits mention of irreversibility, which would make the context more complete for a destructive action.

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 already provides a description for the id parameter ('The tag ID to delete'), giving 100% coverage. The description itself adds no additional parameter-level context, so it stays at the baseline without enhancing understanding 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 'Delete a tag' with a specific verb and resource. The parenthetical clarifies that subscribers are not deleted, which distinguishes this tool's scope from potential cascade deletes. Given sibling tools like create_tag and update_tag, the purpose is 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?

The description implies this tool is for deleting a tag, but it does not explicitly state when to use it or provide alternatives. No exclusions or comparisons to sibling tools are given. The parenthetical is more about behavioral safety than usage guidance, so the usage context is only implied.

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