Get one Gmail thread as a clean transcript

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

With no annotations, the description carries full burden. It discloses that format=full returns plain-text message bodies, explains the stripped parameter's effect on quoted history, and instructs to present message.text verbatim. It does not cover authorization or rate limits but is transparent about core 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?

The description is concise, front-loads the core purpose, and every sentence adds specific value (usage context, format details, verbatim instruction). No fluff or redundancy.

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?

Given 7 parameters and no output schema, the description explains key but not all parameters. It omits accountAlias and chatScope, and does not describe the return structure beyond 'plain-text message bodies.' The format=metadata option is unmentioned.

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?

The schema has 0% description coverage, so the description must compensate. It explains threadId, format (with enum and default), stripped (boolean with behavior), and hints at latestN. However, accountAlias, chatScope, and includeRaw are not described, leaving gaps for parameters that may be important for multi-account scenarios.

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 loads one Gmail thread at a time, specifies it is for use after fetch mode=list, and explains the different format options and stripped behavior. It distinguishes from siblings by indicating this is per-thread and not for batch operations.

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 provides usage context: 'use after fetch mode=list' and 'Call separately per thread.' It also warns against summarizing. However, it does not explicitly exclude scenarios or compare to sibling tools like multi_gmail_get_thread.

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