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

Annotations give the safety profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false), and the description adds real value on top: it discloses the mutation ('mark it read') and warns that message text is untrusted data, plus content limitations (attachments/HTML excluded). It does not mention auth needs or rate limits, but the untrusted-data warning is a useful addition beyond structured fields.

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 tight sentences with the core action front-loaded and a second sentence covering the security/content caveats. No wasted 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?

For a single-message read tool with no output schema and no annotations on return format, the description adequately conveys what is returned ('bounded plain-text message', attachments/HTML excluded). Minor gaps remain around error behavior and how the ID is obtained.

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?

One parameter with 0% schema description coverage, and the description never references emailId or its format. The parameter name is self-evident, so the gap is mild, but the description fails to compensate for the missing schema documentation.

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?

States a specific verb (read) and resource (one plain-text message) with clear scope ('bounded', 'one'). An agent can distinguish this from voidmail_list_inbox without opening the schema, though no sibling is named explicitly.

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 side effect ('mark it read') and content scope imply when to use it, but there is no explicit when-to-use guidance, no prerequisites, and no routing to alternatives like list_inbox for finding IDs first.

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