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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is fully covered. The description adds only that the result includes status and delivery details — useful but thin, and it says nothing about what happens when the ID doesn't exist.

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 no wasted words. It is sized appropriately, though its brevity is partly the source of the missing differentiation rather than pure efficiency.

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?

There is no output schema, so the description must convey the return shape; 'status and delivery details' gestures at it but doesn't enumerate fields. For a simple single-record read with full annotation coverage this is close to adequate, but a bit more on the returned object would close the gap.

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?

Single parameter with 100% schema description coverage ('Email ID (em_xxx)'), so the schema already carries the semantics. The description adds no extra meaning about the ID's format or source; 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?

States a specific verb ('Retrieve') and resource ('a single email') and hints at the returned content ('status and delivery details'), which partially differentiates it from siblings like get-email-body and get-email-raw. However, it never explicitly says it is the email record/metadata view, so the boundary with get-email-meta remains blurry.

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?

No when-to-use guidance and no mention of alternatives, despite five closely related siblings (get-email-body, get-email-meta, get-email-raw, get-email-attachments, get-email). The agent must infer that this is the general record fetch while the others retrieve specific parts.

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