meta_ads_audiences_delete

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

Without annotations, the description fully discloses behavioral traits: destructive impact on ad sets, reversibility window, and the fact that re-creation does not restore the original count. This meets the high standard required for a tool with no annotation support.

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 concise (four sentences) and well-structured, starting with the primary action and return, then outlining consequences, reversibility, and best practices. Every sentence adds value without unnecessary repetition.

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 and no output schema, the description covers all essential aspects: the action, return value, side effects, reversibility, recommended precursor steps, and limitations. This provides complete contextual information for an AI agent to use the tool correctly.

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 has 100% description coverage for both parameters (account_id and audience_id), so the schema already provides detailed semantics. The description does not add further parameter-level meaning beyond what the schema states, earning a baseline score of 3.

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 ('Deletes a Custom Audience') and the return value ('Returns a success flag'). It distinguishes itself from sibling tools like meta_ads_audiences_create, meta_ads_audiences_get, and meta_ads_audiences_list by specifying that it performs deletion.

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 explicit guidance on when and how to use this tool. It warns about the destructive nature, recommends checking ad set usage with meta_ads_audiences_get first, and suggests pausing affected ad sets. It also notes reversibility and limitations, offering a clear decision framework.

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