delete_audience

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

No annotations exist, so description fully bears the burden. It discloses irreversibility, side effect of removing all related data, rate limiting, authentication, dry-run/read-only mode support, and error behavior. No contradictions.

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 thorough but efficient, with clear sections: purpose, side effect, alternatives, usage notes, parameter details, return format. Slightly lengthy but no superfluous content.

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, single parameter, and existing output schema, the description covers all necessary context: operation summary, side effects, safety recommendations, authentication, rate limits, error cases, and return value format.

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?

Input schema has 0% description coverage; the description adds format (10-char alphanumeric), example, source (list_audiences), and a warning to double-check, providing meaning far beyond 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 verb 'delete' and the resource 'audience', and details the full scope of deletion (members, segments, campaigns, stats). It distinguishes from sibling tool 'update_audience' which is for non-destructive changes.

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?

Provides explicit when-to-use (permanent deletion), when-not-to-use (use update_audience for archiving), alternatives (backup via list_audience_members), authentication method (API key), rate limit (10 concurrent), and error handling (404).

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