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

Annotations already establish readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral context that the body comes back truncated ('bounded portion') and that continuation is expected, but says nothing about default/maximum size behavior or what happens at end-of-body.

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 short, front-loaded sentences with zero filler and no repetition of the tool name or title. The second sentence carries the continuation guidance efficiently.

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 annotations covering safety, an output schema carrying the return shape, and 5 parameters, the description covers the truncation/continuation model but leaves the agent without guidance on format selection or size limits. Adequate but with clear gaps for a paging 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?

No annotations beyond safety are given, but the schema is fully self-documenting: format enum, offset, maxChars, accountId, and messageId all carry descriptions or obvious constraints. The description adds one key semantic insight: the offset parameter is a pagination cursor rather than an arbitrary character index, which meaningfully extends the schema. That single insight isn't enough to reach 5, which would require explaining format choice and truncation behavior.

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 states a specific verb and resource ('Read a bounded portion of one email body'), which is concrete and distinguishes it partially from metadata readers. However, it never contrasts itself with sibling tools like get_email or get_thread, leaving the agent to infer why it would pick this over the general message getter.

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 only usage guidance is 'Use nextOffset to continue,' which covers pagination but not tool selection. There is no statement about when to call this instead of get_email, get_thread, or download_attachment.

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