Unsubscribe from all lists.

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is covered by structured data. The description adds no behavioral context of its own: it does not say the action is irreversible, that it affects every list at once, or what happens on partial failure. It adds zero value beyond the name.

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?

It is a single short sentence with nothing extraneous, so it is not bloated. But it is duplicated directly from the title, meaning no sentence earns its place beyond the name itself.

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 an irreversible, bulk destructive mutation with no output schema, the description leaves critical questions unanswered: what counts as "all lists", whether this is scoped to a subscriber, and whether confirmation is required. Annotations cover the safety flag but not the scope semantics an agent needs before invoking.

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 100%, with 'account', 'confirm', and 'id_or_email' all documented in the schema, so the schema does the heavy lifting and baseline 3 applies. The description contributes no additional parameter meaning, but none is required given full coverage.

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?

Tautological: description restates name/title.

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?

There is no guidance on when to use this tool versus narrower removal siblings such as remove_subscriber_from_segments or remove_subscriber_from_workflow, nor any prerequisite or confirmation context. The only hint of usage is the schema's 'confirm' parameter description, which is not part of the tool description.

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