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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: scan contents remain behind the authenticated browser boundary, sender/description metadata must be treated as untrusted correspondence, and the call is idempotent/canonical. That goes meaningfully beyond the annotations.

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?

The core purpose is front-loaded in the opening sentence, which is good. However, the trailing 'Confirmation boundary' sentence enumerates irrelevant operations ('reversible save, explicit fact/evidence record, link preparation, plan refresh') that do not belong to a read tool, reading as templated boilerplate that dilutes the definition.

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 no output schema, the description does carry the return-value burden well by naming the item, handling history, available actions, and browser URL. But for a 3-parameter tool at 0% schema coverage, the unexplained mailItemId and _corply_context leave real gaps.

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% across 3 parameters (companyId, mailItemId, _corply_context), so the description must compensate. 'One exact company's mail item' hints at company scoping, but mailItemId is never explained and the nested _corply_context object is completely unmentioned.

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 first sentence gives a specific verb (Read) and resource (one exact company's mail item) and enumerates the payload: handling history, available actions, and a secure browser URL. This is clearly a single-item retrieval, distinguishing it in spirit from list_mail/list_inbox_messages, though it never names a sibling 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?

It states a prerequisite (authenticated active company access) and a confirmation boundary, which is useful context, but it never says when to choose this over get_corply_mail, read_inbox_message, or list_mail. Usage is implied by 'one exact ... mail item' rather than routed explicitly.

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