Unsubscribe Subscriber

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

Annotations already show non-readonly and non-destructive, and description adds that the write is 'organization-wide' and affects future newsletters. No contradictions; adds 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?

Two sentences, no wasted words. The first states the action, the second explains the consequence. Efficient and 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 output schema exists and the tool is simple, the description covers the essential purpose and effect. It could mention idempotency or error behavior, but the context is sufficient for an agent to use it correctly.

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?

All three parameters are described in the schema (100% coverage). Description adds no additional meaning beyond the schema, so baseline score applies.

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 verb 'Unsubscribe a subscriber' and explains the effect: 'Writes an organization-wide opt-out so future newsletters skip them.' It is specific and distinguishes from sibling tools like 'remove_subscriber' or 'resubscribe_subscriber'.

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 implicitly indicates when to use (for opting out a subscriber without deletion) but does not explicitly contrast with alternatives like 'remove_subscriber' or provide conditions for use. Still, the purpose is clear enough for simple selection.

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