delete_tag

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

With no annotations provided, the description adds value by disclosing that deletion also removes the tag from calls/form submissions. However, it does not mention if the action is irreversible, whether permissions are required, or what happens to dependent data. More behavioral details would improve transparency.

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 extremely concise with two sentences, front-loading the action and key side effect. Every word adds value, and there is no redundancy or filler.

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 the tool's simplicity (delete operation, 2 parameters) and presence of an output schema, the description covers the core purpose and effect. However, it lacks usage guidelines, parameter details, and return value context, making it only minimally complete for an informed agent.

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 0%, yet the tool description provides no additional meaning for the two parameters ('tag_id' and optional 'account_id'). The description fails to explain their purpose, format, or required relationships, leaving the agent with only the schema field names and types.

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 verb 'delete', the resource 'tag', and importantly describes the side effect of removing it from associated calls/form submissions. This distinguishes it from sibling tools like 'update_tag' and 'remove_call_tags', which only remove associations without deleting the tag itself.

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 to use this tool (to permanently delete a tag), but does not provide explicit guidance on when not to use it or mention alternatives like 'remove_call_tags' for removing tags without deletion. It lacks context about prerequisites or scenarios where deletion is appropriate.

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