Get Gmail Threads Content Batch

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

Annotations already indicate read-only, non-destructive, idempotent. Description adds important detail about batching to avoid SSL connection exhaustion, which is beyond annotation scope. No contradictions. Good supplemental context.

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?

Two sentences, front-loaded with main purpose. No superfluous words. Second sentence adds specific constraint. Highly concise 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?

Given presence of output schema (context signal), description need not detail return values. Covers batch limit and format options adequately. No obvious gaps for a batch retrieval 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 has 100% coverage with descriptions. Description adds value by explaining that thread_ids will be auto-batched in chunks of 25, and elaborates on body_format enum values (text, html, raw) with details on conversion behavior. Meaningful additions beyond schema.

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?

Clearly states it retrieves content of multiple Gmail threads in a single batch. Specific verb 'retrieves' and resource 'Gmail threads'. Differentiates from sibling get_gmail_thread_content (singular) and get_gmail_messages_content_batch (messages vs threads).

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 batch limit of 25 threads to prevent SSL exhaustion, guiding usage boundaries. Does not explicitly compare to alternatives like single thread retrieval, but the context of siblings implies when to use batch vs single.

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