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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds a small amount of extra context by noting that draft references are included in the returned thread, but says nothing about pagination, size limits of a thread, or permission requirements.

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 sentences, no filler, with the core verb-resource statement front-loaded. Slightly terse rather than bloated, which is the right failure mode for a simple two-parameter read tool.

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 read-only tool with annotations covering safety and no output schema, the essentials are mostly present. But with 0% schema coverage on two required parameters and no discussion of emailAccountId, an agent lacks enough to map account context confidently.

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%, so the description must carry parameter meaning. It explains the origin of threadId (via browse_mail) but says nothing about emailAccountId, which is equally required and undocumented anywhere. Partial compensation only.

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 complete thread ... for the mail interface') with the notable addition of 'including mailbox draft references'. It clearly differentiates from browse_mail by implying browse_mail produces IDs while this consumes one, though it does not address the sibling read_thread, which an agent could easily confuse with this tool.

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?

It gives explicit prerequisite guidance: 'Use browse_mail to obtain its thread ID', which tells the agent where the required input comes from. It does not, however, state when this tool should be preferred over the similarly named read_thread, leaving one real ambiguity unresolved.

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