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

Annotations already declare the safe read-only profile (readOnlyHint, destructiveHint=false, openWorldHint=false), so the bar is lower. The description adds two genuinely useful behaviors beyond that: results are sorted newest-first, and pagination is driven by a cursor token returned in the previous answer.

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 tight sentences that front-load the resource/ordering before filters and paging. The only waste is the opening 'Reply threads, newest first', which repeats the title verbatim rather than adding information.

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 six-parameter list tool with no output schema and 33% schema coverage, the description is only minimally complete. Cursor semantics ('from the previous answer') are vague, and mailboxId/campaignId/cursor have no explanation in either the schema or the description.

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 only 33%, so the description must compensate. It maps five of six parameters to concepts (unread->view, label->labelId, mailbox->mailboxId, campaign->campaignId, cursor), but adds no format or syntax detail and omits the search parameter entirely.

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 the resource ('reply threads') and its ordering ('newest first') precisely, and names the filter dimensions. It clearly differs from the singular get_thread sibling, though it does not name that alternative explicitly.

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?

Gives useful invocation context: filter by unread/label/mailbox/campaign and page with cursor from the previous answer. However, there is no guidance on when not to use it or when to prefer get_thread or another sibling, so usage is implied rather than fully directed.

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