mail_get_recent_emails

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states it retrieves emails but does not mention if it marks as read, requires authentication, or any side effects. The read-only nature is implied but not explicit.

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 short and front-loaded with a clear purpose, followed by parameter details. Every sentence is useful, though additional guidance on usage would be helpful without being overly verbose.

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 the rich set of sibling mail tools, the description lacks context about which mailbox is queried, whether it returns only the inbox, or how it interacts with other tools. It does not leverage the existence of an output schema to provide completeness.

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?

The input schema has 0% description coverage, but the description provides defaults and brief explanations for the two parameters (days and limit), adding meaning beyond the schema. However, it does not describe behavior or constraints like maximum values.

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 clearly states the tool's purpose: retrieving emails received in the last N days. The verb 'get' and resource 'emails' with a time filter are specific, and it distinguishes itself from siblings like mail_search_emails which offers broader search.

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 description implies usage for fetching recent emails but provides no explicit guidance on when to use this tool versus alternatives (e.g., mail_search_emails, mail_get_email). No exclusions or context about inbox or other mailboxes are mentioned.

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