meta_ads_audiences_delete

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

No annotations provided, so description carries full burden. Clearly states destructive nature: ad sets lose targeting and may stop delivering. Also explains non-reversibility and limitations of re-creation. Fully discloses consequences beyond a simple delete.

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?

Three sentences, front-loaded with core purpose. Every sentence provides essential information (purpose, destructive nature, rollback guidance). No fluff.

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 destructive nature and moderate complexity, the description provides enough context for safe use: consequences, pre-checks, rollback option. Missing details on error handling or response structure, but mentions 'Returns a success flag', and no output schema exists. Adequate for this type of tool.

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 coverage is 100%, so baseline is 3. The description does not add additional semantics beyond what's in the schema. The schema already describes account_id format and audience_id purpose, so description doesn't need to repeat.

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?

Clearly states it deletes a Custom Audience and returns a success flag. The verb 'deletes' is specific to the resource 'Custom Audience', distinguishing it from sibling tools like meta_ads_audiences_get or meta_ads_audiences_create.

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 guidance: instructs to first call meta_ads_audiences_get to check ad sets using the audience, consider pausing those ad sets, and record before-state with mureo_state_action_log_append for possible rollback. Also notes that re-creation does not restore original approximate_count.

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