Unsubscribe

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

The description discloses important behaviors: that it only reports by default, that sending requires send=true, and that web links are never fetched. This adds safety context beyond the annotations, which already flag destructiveHint. It aligns with annotations and clarifies side effects.

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 sentences, each adding value: purpose, default behavior, and a safety caveat. No waste, front-loaded.

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?

Covers purpose, side-effect gating, and a safety guarantee, but does not describe the report format or the confirmation requirement for send, which is only in the schema. Given no output schema, this is a minor gap but overall adequate for a moderately complex tool.

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 covers send, folder, and dry_run with descriptions, but uid, confirmed, and uidvalidity lack explanations. The description clarifies the send flag's role but does not compensate for the undocumented parameters, leaving some ambiguity for confirmed and uidvalidity.

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 uses specific verbs 'Report' and 'send' with a clear resource (List-Unsubscribe header). It distinguishes from sibling tools like 'send' or 'reply' by focusing on unsubscribe semantics and explicitly notes that web links are never fetched.

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 states when the tool reports only versus sends (unless send=true), and notes web links are never fetched, which guides usage. However, it does not explicitly mention alternatives or when not to use it, though the unique purpose is clear enough.

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