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

Annotations already establish a safe read (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the bar is lower. The description adds meaningful behavioral context: the Pro entitlement requirement, the exclusion rules (newsletters, no-reply senders, self-notes), that drafts never count, and the newest-first ordering. It omits pagination/limit 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?

Dense but well organized – direction semantics are front-loaded and each clause carries information (exclusions, draft handling, ordering). It is on the long side for a four-sentence block, but almost nothing is filler.

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?

An output schema exists, so return values need no explanation, and the description covers the search semantics plus the Pro entitlement. The only real gap is the undocumented `limit` and `account` parameters, which matters because the schema itself provides no descriptions.

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 full burden. It thoroughly explains `days` and both values of `direction`, but says nothing about `limit` or `account`, leaving two of four parameters undocumented in either place.

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 ('Threads waiting on a reply') and precisely defines what qualifies via the two direction modes. An agent can distinguish it from search_mail, show_mail, and get_thread without opening any schema.

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 when each mode applies and points to the follow-up tool ('Use get_thread on a result for the whole conversation'), which is explicit routing. It does not, however, contrast itself with sibling search/list tools like search_mail or show_mail, so the alternative-selection guidance is partial.

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