get_email_html

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

Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds crucial security context: the HTML is sanitized and remote loading is disabled. This goes beyond annotation coverage and is highly relevant for safe execution.

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 short clauses deliver the core purpose and safety behavior with no wasted words. The description is front-loaded and effectively structured.

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 read-only tool with strong annotations and an existing output schema, the description covers purpose, behavioral constraints, and usage guidance. The missing parameter explanations are standard identifiers and can be inferred from sibling tools and the schema itself.

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?

The description provides zero information about the four required parameters (account_id, mailbox, uid_validity, uid). With 0% schema description coverage, the description was expected to compensate, but it does not mention any parameters or their relationships.

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?

Description explicitly states 'Read sanitized HTML' – a specific verb and resource. It also distinguishes from the sibling tool get_email by recommending the plain-text alternative, making its unique purpose clear.

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 phrase 'prefer plain-text get_email' explicitly names an alternative and implies when not to use this tool. The additional 'without remote loading' gives a clear safety-oriented use case for choosing HTML.

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