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

Annotations already declare destructiveHint=true, and the description adds 'Permanently' and 'Irreversible' which reinforces the destructive nature but adds little new info. However, it does disclose the bulk deletion capability, which is a behavioral trait not evident from annotations. It omits details about auth requirements or failure modes, but for a delete operation, the core behavior is clear.

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—two sentences containing only essential information: what the tool does and its bulk capability. There is zero fluff or redundant wording. Every word adds value, and the structure front-loads the primary purpose.

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 destructive operation with 3 parameters and no output schema, the description covers the core action and bulk mode but omits critical context: prerequisites (e.g., authentication requirements), behavior on failure, and the role of the required auth_account parameter. While the simplicity of deletion mitigates the need for extensive documentation, the lack of any parameter semantics for auth_account and no mention of return behavior leaves gaps.

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%, so the description must compensate. It mentions `audience_id` implicitly via the action and explicitly states `audience_ids` for bulk execution, but it does not explain `auth_account` at all. The distinction between single and bulk is useful but incomplete—no details on parameter formats, constraints, or relationships. With 3 parameters and only one partially explained, the description falls short.

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 action: 'Permanently delete a Custom Audience.' This is a specific verb+resource combination that distinguishes it from sibling delete tools for adsets, campaigns, and creatives. It unambiguously identifies the target resource and the irreversible nature of the operation.

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 usage by naming the exact action, but does not explicitly state when to use this tool versus alternatives or mention any prerequisites. The bulk support note ('accepts audience_ids for batched execution') provides usage context for deleting multiple audiences at once, but there's no when-not-to-use guidance or references to sibling tools.

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