dex_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 key behavioral traits: the deletion is 'permanent' (irreversible) and has side effects ('removed from all contacts it was assigned to'), which is crucial for a destructive operation. However, it does not mention permissions, rate limits, or error handling.

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 concise sentences with zero waste: the first states the action and permanence, the second explains the side effect. It is front-loaded with the core purpose and efficiently conveys necessary 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?

Given a destructive tool with no annotations and no output schema, the description is reasonably complete: it covers purpose, permanence, and side effects. However, it lacks details on permissions, error cases, or confirmation requirements, which would be helpful for safe 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 input schema has 1 parameter with 0% description coverage, so the description must compensate. It clarifies that 'tagId' refers to the tag to be deleted and implies it identifies a specific tag, but does not specify format or sourcing details. This adds meaningful context beyond the bare 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 ('permanently delete') and the resource ('a tag'), and distinguishes it from siblings by specifying the effect on contacts ('removed from all contacts it was assigned to'), unlike other delete tools (e.g., dex_delete_contact, dex_delete_group).

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 usage for deleting tags, but does not explicitly state when to use this tool versus alternatives (e.g., dex_update_tag for modification or dex_manage_contact_tags for tag management). It provides some context about the effect on contacts, but lacks explicit guidance on prerequisites or exclusions.

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