Delete a tag

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

Beyond the annotations, the description reveals important behavior: removing the tag from every contact, preserving contacts, and being idempotent even for nonexistent tags. This gives an agent a clear mental model of what happens when the tool is invoked.

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 compact and front-loaded: the primary action and cascade effect come first, followed by two essential clarifications. Every sentence earns its place without redundancy.

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 two-parameter destructive operation, and the description covers the core scope, side effects, and idempotence behavior. With no output schema required and annotations already marking destructiveness, nothing essential is missing.

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?

Schema description coverage is 100%, so the baseline is 3. The schema provides parameter names and types, and the description adds little beyond implying that the tag exists within a profile context. The parameter descriptions themselves are minimally informative but the schema still covers them.

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 states a specific action ('Delete a tag') and the exact resource affected, including the cascade behavior ('remove it from every contact carrying it'). This clearly distinguishes it from related tag tools like reach_renameATagV1 or reach_removeAContactFromATagV1.

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 when the tool should be used, but does not explicitly mention alternatives or state when not to use it. The note that contacts are not deleted is useful context, but there is no direct routing between this and the other tag-related siblings.

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