get_mailbox_stats

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

Discloses caching behavior and sampling (up to 200 recent emails), but does not explicitly state read-only nature or side effects. With no annotations, the description partially fulfills this need.

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?

Three concise sentences, each adding value—no filler, well structured.

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?

Covers purpose, caching, sampling, and a parameter hint, but lacks output format specifics since no output schema is provided.

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 0%; description clarifies mailbox_id via mention of list_mailboxes, but does not explain account_id, leaving some ambiguity.

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 it provides stats (total count, top senders, top subjects) for a specific mailbox folder, distinguishing it from sibling tools like list_mailboxes and get_email.

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?

Advises using list_mailboxes to find mailbox_id, which is helpful but does not explicitly mention when not to use this tool or alternatives.

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