ad_manager_fb_delete_custom_audience

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

Annotations already disclose destructiveHint=true and idempotentHint=true, so the description is not required to repeat those. The description adds no extra behavioral context such as permanence or effects on related entities, but it is consistent with the annotations. No contradiction exists.

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 a single, efficient phrase 'Delete custom audience' with no wasted words. It is front-loaded and immediately conveys the action, though it lacks any supplementary detail that could enhance clarity.

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 simple operation (delete by ID), the annotations covering destructive and idempotent behavior, and the schema documenting all parameters, the description is sufficient for an agent to invoke the tool correctly. No return value is needed, and no complex caveats are evident.

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 input schema provides 100% coverage with descriptions for both parameters (audienceId and locationId). The description adds no parameter-specific semantics beyond what the schema already states, so the baseline of 3 is 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 states a specific verb ('Delete') and a specific resource ('custom audience'), which clearly identifies the operation. It is unambiguous and distinct from siblings like 'ad_manager_fb_remove_custom_audience_member' or 'ad_manager_fb_update_custom_audience'. However, it does not explicitly contrast with similar delete tools, so it is not a 5.

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 provides no guidance on when to use this tool versus alternatives, no prerequisites, and no mention of appropriate contexts. An agent receives no instructions for selection or exclusions, so it earns a low score.

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