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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. 'Saved outgoing email' adds only slight context (persisted sent mail) and says nothing about the format switch, missing/deleted messages, or attachment handling.

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?

One short, front-loaded sentence with zero padding, which is structurally clean. But the brevity is under-specification rather than economy — the same single sentence could have carried the key disambiguation with only a few more words.

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?

An output schema exists, so return-shape explanation is rightly absent. Still, for a read tool in a crowded get_* family, the description omits the id source, the format behavior, and the boundary against get_message, leaving real gaps that the schema cannot fill.

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 50% and the uncovered parameter is message_id, which the description never mentions (no hint that the id must come from list_sent/get_thread). The format parameter's meaning is documented richly in the schema, but the description contributes nothing to either parameter.

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 clear verb+resource ('Read a saved outgoing email'), so an agent knows it retrieves a stored sent message. However, it draws no boundary against the very close sibling get_message (or list_sent), so selection between sent-message reads and general message reads is left to the agent to infer from the name alone.

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?

There is no when-to-use guidance, no prerequisite (e.g., needing a message_id from list_sent), and no mention of the alternative get_message for non-sent mail. The description offers no context beyond the bare purpose.

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