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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuine value beyond that: which fields come back and the sort order. It stops short of covering pagination or result-size behavior, which matters for a list tool.

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 short sentences with zero filler; the read marker and resource come first and the cross-reference follows. Every clause carries information.

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?

With no output schema, listing the returned fields is a real contribution and the cross-reference helps the agent chain calls. However, for a paginated list tool it omits any account of paging behavior or total counts, leaving a notable hole.

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 coverage is 0% for two parameters (page, per_page), and the description never mentions pagination, page size, defaults, or limits. 'Newest first' hints that paging is meaningful but gives no semantics for how to drive it.

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?

States the resource precisely ('Saved recipient lists') and enumerates the returned fields (name, description, number of addresses) plus ordering ('newest first'). It is distinguishable from list_email_list_members and create_email_list by the resource noun, though it never explicitly contrasts itself with those siblings.

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 gives a useful next-step pointer ('A list can be added to any draft campaign with import_email_campaign_recipients'), which implies the workflow context. But it does not say when to use this versus alternatives like list_email_list_members, nor any exclusions or prerequisites.

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