Get Received Email

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

Description discloses return content (HTML, plain text, headers, download URL) but no annotations provided; missing side effects, auth, or error handling.

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?

Single sentence, front-loaded with action and resource, efficient but could benefit from bullet points for structure.

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?

Adequate for simple retrieval with one parameter; no output schema but description lists returned elements. Missing details like pagination or field format.

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 covers 100% of single parameter 'id'; description adds minimal extra value beyond stating 'by ID'.

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 clearly states it retrieves full details of a specific received email by ID, listing included content. Distinct from siblings like get-received-email-attachment and list-received-emails.

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?

Implies use case (retrieve by ID) but no explicit guidance on when to use vs. alternatives like get-email or list-received-emails.

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