get_recent_emails_all_folders

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

With no annotations provided, the description carries full burden. It transparently states the operation is a fetch (read-only), describes the return format (bodyPreview instead of full HTML), and lists exclusions. It does not mention any side effects or error conditions, but as a read operation, those are not expected. The description is sufficiently transparent about the tool's behavior.

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 two sentences, covering the core functionality and key exclusions without unnecessary detail. Every word contributes to the meaning, and there is no repetition or fluff.

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 straightforward read operation, the description provides sufficient context: what it fetches, from where, what it excludes, and what the response contains. It does not require additional explanation about return format or filters. It could be slightly more explicit about sorting order, but that is a minor omission given the simplicity of the tool.

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 schema covers both parameters (limit and mailbox) with descriptions. The tool description does not add any additional semantics beyond the schema, so the baseline of 3 is appropriate. No extra nuance is provided that would elevate the score.

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?

Clearly states the tool fetches recently received emails across all folders, explicitly distinguishing it from the sibling get_recent_emails by noting 'all folders, not just Inbox'. The exclusion of Deleted Items, Junk, and Drafts further refines the scope.

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?

Provides explicit guidance on when to use this tool by contrasting with the Inbox-only variant and listing the folders that are excluded. Also mentions the bodyPreview payload choice, which helps the agent decide based on response size needs. Does not explicitly state 'use this when you need emails from any folder except exclusions', but the implication is clear.

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