meta_delete_custom_audience

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

The description adds behavioral context beyond the schema by noting the operation is 'destructive — removed, not archived'. This is helpful since no annotations are provided. However, it could further clarify irreversibility or permission requirements.

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 very concise, at 12 words including a tag, and front-loads the [Meta][WRITE] prefix for quick identification. It could be slightly more structured but is appropriately brief.

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 simple one-parameter destructive operation with no output schema, the description covers the essential behavioral aspect (destructive, not archived) and the service context. It is largely complete, though it could mention the response (e.g., success/failure).

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 single parameter 'audienceId' has no description in the schema (0% coverage), and the description does not elaborate on its format, constraints, or source. The agent receives no additional meaning beyond the raw 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 'Delete a custom audience' with a specific verb and resource. It also distinguishes from sibling tools like meta_list_custom_audiences (list) and meta_update_campaign (update) by explicitly noting it's a write/delete 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 does not provide explicit guidance on when to use this tool versus alternatives, nor does it mention any preconditions or exclusions. The destructive nature is implied, but no contextual advice is given.

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