delete_audience

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

Annotations declare destructiveHint=true and idempotentHint=true. Description adds side effects ('removes every member and historical data'), irreversibility, error case (404 if list_id not found), and idempotent behavior (delete already deleted returns error). Goes beyond annotations.

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?

Very concise and well-structured: first sentence states action and scope, then side effect, alternative, backup advice, error info, and finally Args/Returns sections. No wasted words, each sentence earns its place.

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 destructive nature, the description covers prerequisites (list_id from list_audiences), side effects (cascading deletion), error handling (404), return format (JSON with status), and alternatives. Combined with annotations and output schema, it is fully complete for an AI agent to use safely.

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 coverage is 0%, but the description explains the required list_id parameter with format ('10-char alphanumeric'), example, source (list_audiences), and caution. The optional account parameter is not described, but it is optional and defaults to null; the main parameter is well-covered.

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 begins with 'Permanently delete an audience and all its members, segments, campaigns, and stats', which is a specific verb and resource with scope. It distinguishes from sibling delete tools by detailing cascading effects and from update_audience by noting it is for archiving. Purpose is crystal clear.

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?

Explicitly states when to use this tool (permanent deletion) and when not to, advising alternative tools like update_audience and listing backup steps with list_audience_members. Also notes prerequisite: obtain list_id from list_audiences.

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