unsubscribe_member

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

Annotations already indicate non-read-only, non-destructive, but description adds that it preserves history, is reversible, and returns 404 on missing member. Adds useful context beyond annotations.

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?

Six sentences covering purpose, reversibility, alternatives, error condition, and parameters in bullet points. No wasted words, well-structured.

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 context (annotations, output schema described, sibling tools), the description covers behavior, parameters, return format, error handling, and usage guidance comprehensively.

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 has 0% coverage, but description provides detailed semantics for list_id (10-char alphanumeric, example, how to obtain) and email_address (valid email, must exist). However, the optional 'account' parameter is not described, so not fully complete.

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?

Description clearly states the tool unsubscribes a member from an audience while preserving profile and history. It distinguishes from siblings like delete_member (permanent removal) and update_member (reversible), making the purpose specific.

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?

Explicitly provides when to use (unsubscribe), when to use alternatives (delete_member for GDPR, update_member to reverse), and notes the 404 error condition for non-existent members.

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