list_emails

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

No annotations are given, so the description must carry the burden of behavioral disclosure. It states 'list' (implying read-only) but does not explicitly confirm no side effects, mention rate limits, or describe pagination behavior. This is insufficient for a potentially large operation.

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?

The description is a single sentence, which is concise but minimal. It is appropriately sized for a simple list operation, but could be more informative without being verbose (e.g., mentioning result set structure).

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?

Given no annotations and no output schema, the description is too brief. It does not clarify the return format (e.g., array of email objects), whether pagination is supported, or how sorting works beyond the 'ascending' param. For a list operation, more context is needed.

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% (all parameters documented), so baseline is 3. The description adds no extra meaning beyond what the schema already provides (e.g., mailboxId, limit, ascending defaults).

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 'List emails from a mailbox' is a clear verb+resource combination. It distinguishes from sibling tools like 'get_email' (single email) and 'search_emails' (filtered search), though it could be more specific about scope (e.g., listing all vs. filtered).

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?

No guidance is provided on when to use this tool versus alternatives like 'search_emails' or 'get_recent_emails'. The description does not mention context, prerequisites, or when not to use it.

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