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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds genuine domain context by explaining how addresses end up on the list (opt-out link or manual entry), but says nothing about pagination behavior or volume.

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?

A single front-loaded sentence with the '[read]' tag first and no wasted words. It is efficient, though its brevity tips into under-specification rather than tight completeness.

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?

For a simple read-only listing tool with no output schema, the description covers what the resource is but omits the two things an agent actually needs: how paging works and what fields each record returns. Adequate but with clear gaps.

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 description coverage is 0% for both parameters (page, per_page), and the description contributes nothing about paging — no default page size, ordering, or total-count behavior. With two undocumented parameters the description should compensate and does not.

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 defines the resource precisely — addresses that must never receive campaign mail again — and the '[read]' prefix signals the operation type. It does not explicitly say it returns a paginated list, nor distinguish itself from siblings like add_email_unsubscribe or list_sms_optouts/list_voip_optouts, leaving that to the tool name.

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?

No when-to-use guidance is given. It never states that this is the read counterpart to add_email_unsubscribe, nor when to prefer this over list_email_lists or the SMS/VoIP opt-out lists. The agent must infer usage from the name alone.

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