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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context: results are a single bounded page, pagination is handled by the MailerCheck API, and no response links are followed. That last point is valuable because it tells the agent not to expect a next-page URL.

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?

Three short sentences, no filler, with the core read scope front-loaded before the exclusions and pagination caveat. Every sentence carries distinct 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?

For a read-only list tool with no output schema, the description tells the agent what data comes back (summaries, status, statistics) and that paging is API-side, which is adequate. The remaining gap is pagination semantics, which the description hints at but does not define.

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%, so the description must carry parameter meaning, but it only alludes to a 'bounded page' without explaining page numbering, limit, defaults, or the 1-100 cap. The agent gets no help on how to paginate from the prose.

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 uses a specific verb (read) with a specific resource (one bounded page of list summaries, processing status and statistics), which is clearly distinct from mailercheck_get_list's single-list fetch. It does not name that sibling explicitly, but the scope is 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?

The negative scoping sentence ('Does not create, verify or delete lists') usefully rules out mutation, and 'one bounded page' implies enumeration. However, it never states when to choose this over mailercheck_get_list or mailercheck_verification_result, leaving the routing inference to the agent.

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