unsubscribe_member

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

No annotations are present, so the description fills the gap. It discloses authentication via API key, max 10 concurrent requests, and read-only/dry-run respect. It does not fully describe rate limits or all implications, but covers key aspects.

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 well-structured with sections, but slightly verbose. Each sentence adds value, yet could be trimmed slightly without loss. Still, it remains efficient.

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 presence of an output schema (not shown), the description adequately covers usage, parameters, behavior, and error case. It is comprehensive for the tool's complexity, though a few details like idempotency are 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?

Despite 0% schema description coverage, the description adds significant meaning: list_id format and source, email_address validity and existence requirement. This goes well beyond the bare schema.

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 action: 'Unsubscribe a member from an audience, preserving profile and history for reporting.' It distinguishes from sibling tools like delete_member and update_member, making the purpose unambiguous.

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?

Explicit usage guidance is provided: reversible via update_member, permanent removal via delete_member. Also mentions 404 error for non-existent members, giving clear when-to-use vs alternatives.

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