Delete a tag by UUID to remove it from all contacts and clear outdated or incorrect labels across the account.
Delete a tag. Removes the tag from all contacts.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Tag UUID |
Changes observed during successful MCP inspections.
v4.71.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It discloses the critical destructive scope by saying the tag is removed from all contacts, but it does not mention irreversibility, required permissions, or what happens to the tag record itself.
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 with no waste. The action is front-loaded, and the second sentence immediately clarifies the scope of deletion.
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 simple one-parameter deletion tool with no output schema, the description gives the essential action and effect. It is nearly complete, though a destructive mutation tool with no annotations would benefit from explicitly warning about irreversibility or required permissions.
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 has 100% description coverage for the single 'id' parameter ('Tag UUID'), so the schema already documents the parameter fully. The description adds no additional parameter-level syntax or constraints, making the baseline 3 appropriate.
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 uses a specific verb and resource ('Delete a tag') and adds the key consequence that the tag is removed from all contacts. This makes the operation clear, but it does not explicitly name or distinguish against nearby sibling tools such as conduyt_bulk_untag_contacts or conduyt_merge_tags.
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 states what the tool does but gives no explicit guidance on when to use it versus alternatives. The global-removal consequence implicitly suggests permanent tag deletion rather than contact-level untagging, but there is no stated when/when-not rule or named alternative.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.