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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description usefully adds ordering ('newest first') and scope (inbox plus sent mail), but says nothing about pagination, default limit behavior, or result shape.

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 zero filler and the scope stated before the ordering. It is efficient, though arguably too terse for a 4-parameter tool with 25% schema coverage.

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 and ample annotation coverage, the main gap is the four parameters: limit, direction, and since_seconds are only obliquely suggested. It is minimally adequate to call the tool but not sufficient to call it precisely.

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 only 25% (just unread_only), so the description needs to carry weight. It partially does: 'inbox (and sent mail)' maps to the in/out direction enum and 'recent' hints at since_seconds/limit, but the limit param and the enum values remain unexplained.

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 clear verb ('List') and resource ('emails') plus scope ('agent's inbox and sent mail') and ordering ('newest first'). It doesn't explicitly distinguish itself from siblings like read_email or list_messages, so an agent must infer the boundary rather than being told.

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?

Usage is only implied by the scope wording; there is no explicit when-to-use guidance, no stated relationship to read_email (to view one email) or send_email, and no conditions for choosing this over list_messages. The agent must infer routing from the sibling names alone.

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