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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description adds real behavioral value beyond that: results are newest-first and message bodies are omitted from the response, which tells the agent what it will and won't receive.

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?

Compact and front-loaded — read-only marker, resource and scope first, then filter semantics in semicolon-separated clauses. Dense but every clause carries information; only the pagination omission keeps it from being fully economical.

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 8 optional parameters, no output schema and zero schema descriptions, the description supplies nearly everything needed to call it: folder values, id/uuid alternatives, search target, ordering and body omission. Gaps are minor — pagination defaults/semantics and whether a zone identifier is effectively mandatory.

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 carries the burden and mostly does: it explains the zone id/uuid pair, the account id/uuid narrowing, the q search scope (subject/from/to/snippet), and enumerates the valid folder values that the schema leaves as a bare string. Only page and per_page go undocumented.

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 messages) scoped to one e-mail zone, with ordering ('newest first') and payload shape ('bodies left out'). It does not explicitly name the sibling to use for full message content (get_email_message / get_email_thread), so the differentiation is inferred from 'bodies left out' rather than stated.

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 implied: use this to enumerate messages in a zone, narrowed by folder or mailbox, with q for text search. There is no explicit when-to-use / when-not-to-use statement and no routing to alternatives such as get_email_message for a single message or get_email_thread for a conversation.

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