Delete Saved Audience

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

Annotations already declare destructiveHint: true, so the description adds no new behavioral information. It does not elaborate on consequences (e.g., permanent deletion, impact on related campaigns) or required permissions beyond what's implied by the action.

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 extremely concise, using one sentence plus a bullet for the argument. It is front-loaded with the action. However, the structure is minimal and lacks any formatting that aids readability.

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 simplicity (one parameter, no output schema, no nested objects), the description covers the basic operation. However, it omits important context such as error scenarios, idempotency (idempotentHint: false), and whether the audience must exist. It is minimally adequate.

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 description coverage is 0%, so the description should add meaning to the parameter. It only repeats the parameter name and type ('audience_id (string): Saved audience ID'), providing minimal additional context. The label 'Saved audience ID' is a slight improvement but insufficient to compensate for the lack of schema description.

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') and resource ('a saved audience'). The verb+resource combination is specific and leaves no ambiguity about what the tool does, distinguishing it from siblings like create or list saved audience.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., meta_list_saved_audiences to find the ID, or meta_create_saved_audience to create). There is no mention of prerequisites, such as the need to have a valid audience_id, or that the action is irreversible.

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