meta_ads_audiences_delete

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

With no annotations, the description fully discloses the destructive nature: 'Destructive — any ad sets currently targeting this audience lose the targeting source and may stop delivering.' It also explains rollback limitations (re-creation does not restore approximate_count).

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?

Multiple sentences but each adds essential information: action, return, destructive warning, rollback info, and actionable recommendations. Well-organized with critical warnings upfront.

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?

The description covers preconditions (check ad sets), consequences (delivery stop), post-action behavior (success flag), and recovery options (rollback). No output schema exists, but 'success flag' is sufficient. All necessary context is present.

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?

Although schema coverage is 100%, the description adds valuable context: for account_id, it explains format and optional fallback; for audience_id, it specifies 'Audience ID to delete.' It also ties into the rollback tool, providing extra meaning 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 'Deletes a Custom Audience. Returns a success flag.' It specifies the action (delete) and resource (Custom Audience), and distinguishes from sibling tools like meta_ads_audiences_get by including a recommendation to call that first.

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 advises to call meta_ads_audiences_get first to check which ad sets use the audience, and suggests pausing those ad sets. It also mentions rollback via rollback_apply, giving clear guidance on when and how to use the tool.

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