List inbox threads or batch-fetch (legacy)

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

With no annotations, the description carries full burden. It discloses that snippets are not full bodies, that full mode batch-loads and auto-drafts (token-heavy), and that nothing is sent automatically. It does not cover rate limits or auth but is otherwise transparent.

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 moderately concise, front-loading the recommendation and key constraints. Some redundancy exists (e.g., 'Nothing is sent automatically' repeats from param descriptions). Still, it remains readable and 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?

With 9 parameters and no output schema, the description covers the core use case well, explaining modes, query modes, and key behavioral constraints. However, it omits details on many parameters and does not describe the output format.

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%. The description explains mode and queryMode enums but does not cover 7 other parameters (maxResults, includeLatestBody, saveGmailDrafts, writeMarkdownFile, accountAlias, chatScope, query). Only 2 of 9 parameters get semantic explanation, insufficient for full understanding.

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 the tool lists inbox threads or batch-fetches. It distinguishes modes (list vs full) and recommends list for triage, effectively differentiating from sibling tools like fetch, get_thread, etc.

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 when-to-use guidance: uses list for triage, advises to use get_thread for full bodies, warns against full mode for normal review, and explains queryMode for sent/archives. Also tells agents not to summarize or load multiple full threads.

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