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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds real value beyond that by scoping the blast radius: published pages previously sent to this audience survive the deletion. It stops short of saying whether deletion is reversible or what happens if the audience is in active use.

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?

Two short sentences, zero waste, with the action stated first and the caveat second. Every clause earns its place.

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 destructive, single-parameter tool with no output schema, the description covers what is removed and what is preserved, but says nothing about irreversibility, failure modes, or the expected response. Annotations carry part of that load, so it is adequate rather than complete.

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?

There is a single required parameter, id, at 0% schema description coverage, and the description never mentions it. The meaning is inferable from the tool name (an audience identifier), so the gap is small, but the description adds nothing over the bare 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 gives a specific verb (Remove) and resource (saved audience) plus the workspace scope, which clearly separates it from get_audience and save_audience. It does not explicitly name those siblings, but the resource is unambiguous.

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 second sentence, "Does not delete previously published pages," implicitly distinguishes this from delete_page and signals when this is the right tool versus a page deletion. There is no explicit statement of prerequisites, when-not-to-use, or what to do if the audience is still referenced.

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