Retrieve an email message body as HTML to view formatted content. Supply the message ID, with optional folder and account for multi-account support.
Read an email message body as HTML. Useful for formatted emails.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Email message ID | |
| folder | No | Folder name (default: INBOX) | |
| account | No | Account name (uses default if omitted) |
Changes observed during successful MCP inspections.
v1.7.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided. Description explains the core behavior (reads HTML body) but does not disclose details like permissions, error handling, or return format. Adequate but lacks depth.
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 sentences with no wasted words. Front-loaded with verb and resource. Highly efficient.
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?
Given no output schema and no annotations, the description is minimally adequate. It explains the action but lacks details about return values or constraints. Could be more complete.
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 coverage is 100%, so the schema already documents parameters. The description adds no additional meaning beyond schema, so 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?
Clearly states verb (read) and resource (email body as HTML). Distinguishes from siblings like read_email (likely plain text) and read_thread.
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?
Mentions 'Useful for formatted emails,' which hints at when to use this over alternatives, but does not explicitly state when not to use it or name specific alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.