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

Goes well beyond the readOnly annotation by disclosing the decoding strategy (plain-text part preferred, else HTML converted to text) and the truncation behavior with a flag that the result indicates it was cut. This is exactly the kind of output-shape context annotations cannot convey; only the limit value itself is left unspecified.

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 the core action, then the decoding rule, then the truncation caveat. Every clause carries information an agent would otherwise have to guess.

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 an output schema present, return structure is covered elsewhere, and the description adds the two behavioral facts that matter most (format conversion and truncation). The only real gap is the unaddressed relationship to the sibling `read_email`.

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 coverage is 100% and each of the three required parameters is documented in the schema, including how the UID relates to list/search tools. The description adds nothing about parameters, so the baseline 3 applies.

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?

Specific verb+resource ('Read the full text of one email') with an explicit scope qualifier ('one email'), so the agent knows it fetches a single body rather than a list. It does not, however, differentiate itself from the sibling `read_email`, which by name sounds like it does something very similar.

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?

Usage is only implied: the agent can infer it should call this when it needs the decoded body of a specific UID. There is no explicit when-to-use statement and no guidance on choosing this over `read_email` or `list_emails`.

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