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

The annotations already declare read-only, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds useful context beyond annotations by noting the HTML includes tables, font fallbacks, and dark mode, and by mentioning the Pro/free-flows availability condition.

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 description is short and front-loads the key resource and source. Every fragment contributes useful information about what the HTML contains, why to use it, and availability, with no wasted text.

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 simple one-parameter, read-only retrieval tool with rich annotations and full schema coverage, the description provides enough context to call it correctly. The only minor gap is that the availability phrase 'Pro, or this week's free flows' is terse and not fully explained.

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?

There is only one parameter and schema description coverage is 100%, so the schema already documents emailId as coming from search_emails. The description reinforces that source but does not add further meaning such as format, validation, or lookup behavior, so the baseline 3 is appropriate.

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 clearly identifies the resource as the original HTML of one email from search_emails, which distinguishes it from the sibling search tool. It is specific about scope and content, though the action verb is only implied by the tool name rather than stated in the description itself.

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 gives a clear use case: adapt the retrieved HTML to the user's brand instead of writing email HTML from scratch. It also implies the prerequisite that the emailId comes from search_emails, but it does not explicitly state when not to use it or detail other alternatives.

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