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

Goes well beyond the annotations (destructiveHint=true, idempotentHint=false): it discloses the suppression-list side effect, the channels affected, that the record persists rather than being deleted, and that the change cannot be reversed via the API. That irreversibility and the persistence detail are exactly the behavioral facts an agent needs before calling a destructive tool.

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 tight sentences, each carrying distinct information — effect, persistence rationale, irreversibility — with the primary action front-loaded and no filler.

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 one-parameter destructive mutation with no output schema, the description supplies the side effects, irreversibility, and the deletion distinction that the annotations alone do not convey. Nothing material is missing for correct invocation.

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 0% and the single `email` parameter is undocumented in the schema; the description only obliquely refers to 'an address', adding no format, validation, or source guidance. With one obvious parameter this is not fatal, but the description does not compensate for the coverage gap.

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?

States a specific verb (unsubscribes) plus the exact resource behavior (adds the address to the workspace suppression list) and names the downstream effect (no more campaigns, automations, or sends). It is clearly distinguishable from siblings like erase_subscriber and add_suppression because it explains the suppression-record mechanic.

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?

Gives clear context for when this is the right call ('record is not deleted — that is what prevents the address from coming back on the next file import'), which implicitly steers the agent away from erase_subscriber. It stops short of explicitly naming the alternative tool or stating when-not-to-use, so it is not a 5.

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