Unsubscribe

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

Beyond annotations, the description explains the exact attempt order (RFC 8058, email, browser, none), clarifies that it deletes nothing, and describes the return method. This adds significant behavioral context not present in annotations, and does not contradict them.

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 structured with a numbered list for the method attempts, and every sentence adds value: the method order, the 'deletes nothing' note, and the parameter preference. It is detailed without being verbose.

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 complexity (multi-step unsubscription), the description covers the full behavior, the return value possibilities, and the parameter source. The output schema presumably documents the return structure, and the description fills in the behavioral nuances. Nothing essential is missing.

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?

While the schema already fully describes the id parameter (100% coverage), the description adds practical context by recommending the lastMessageId from mail_senders_summary as the source, which helps the agent pick the right value. This goes beyond the schema's generic 'Id of a representative message'.

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 tool's purpose: unsubscribing from a mailing list, with a specific verb 'unsubscribe' and a resource 'mailing list of a message'. It distinguishes itself from sibling tools (list, search, move, delete) by focusing on unsubscription, and outlines a concrete method sequence.

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?

It provides clear context on when to use (for unsubscribing) and even recommends passing the lastMessageId from mail_senders_summary, which is useful guidance. However, it does not explicitly state when not to use it or name an alternative tool, so it stops short of full explicit guidance.

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