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

With no annotations, the description carries the burden and does disclose meaningful behavior: these emails are never delivered, results are ordered newest first, and the single-id lookup exposes html/text including a verify_start code. It stops short of auth/rate-limit/error behavior, but covers the essential traits.

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 dense sentence that front-loads the key behavior (never delivered, newest first) before the parameter modes. It is slightly run-on with stacked colons and parentheticals, but 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?

For a simple read-only list tool with no output schema and no annotations, the description covers what is returned, ordering, delivery status, and the single-record mode. Pagination/auth details are absent but limit is handled by the schema.

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 100% (baseline 3), and the description adds value beyond the schema by explaining what the id lookup actually returns (one email with html and text, plus a verify_start code) and what to does (filter by recipient). limit is left entirely to the 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?

States a specific verb+resource (list test messages) and immediately characterizes them: sent with a test key, accepted, stored, never delivered. It is clearly distinguishable from the send/verify siblings, though it never names a sibling tool explicitly.

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 implies two usage modes (list all vs. fetch one by id, or filter by recipient) but gives no explicit when-to-use/when-not guidance or named alternatives among the many sibling tools. Usage must be inferred from the behavior description.

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