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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds only product framing about a 'unified inbox' and nothing behavioral such as pagination or result limits, despite the 'limit' parameter existing. Value beyond annotations is minimal.

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 sentences, of which the first merely restates the title and the third is marketing copy about the product ('unified inbox combines transactional reply threading...'). Only the second sentence carries real information, so there is meaningful waste despite the compact length.

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?

With no output schema, the description does not describe the return shape, and it omits pagination/cursor behavior even though a 'limit' parameter and 200 maximum imply paging. Safety and parameters are adequately covered by annotations and schema, but return/usage behavior is left implicit for a listing 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?

Schema description coverage is 100%, so the schema already documents all six parameters, establishing a baseline of 3. The description's filter list maps to state, mailboxId, label, and search, but it also cites a 'screener status' filter that does not exist as a schema parameter, which introduces mild confusion rather than added precision.

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 clear verb+resource ('List inbox conversations') and enumerates the filterable dimensions, so an agent can tell it's the list endpoint. However, it does not explicitly distinguish itself from siblings like get_convo, list_inbox_counts, or list_messages, leaving the agent to infer which of several conversation-related read tools to pick.

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 filter enumeration implies when the tool is useful (broad filtered conversation listing), but there is no explicit when-to-use guidance, no mention of alternatives (get_convo for one, list_inbox_counts for aggregates), and no stated prerequisites. Usage is implied rather than directed.

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