List Received Emails

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

Annotations are absent, so the description carries the full burden. It states the tool returns paginated metadata but does not explicitly disclose it is read-only, non-destructive, or detail authentication requirements. While the purpose implies a safe read, more explicit behavioral context would be helpful.

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 concise and well-structured with bold headings for purpose and exclusions. Two paragraphs cover key points without waste.

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 annotations and no output schema, the description explains the scope, pagination, and directs to complementary tool. It adequately covers main usage scenarios but omits error handling or rate limits. Still, it is fairly complete for a list operation.

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 coverage is 100%, providing baseline 3. The description does not add additional meaning to parameters beyond the schema's existing descriptions. It mentions pagination and refers to get-received-email for full content but does not elaborate on parameter usage or semantics.

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 states the action (list), the resource (received emails in inbox), and the context (Resend receiving address). It provides example queries and explicitly distinguishes from sibling tools 'list-emails' and 'list-broadcasts'.

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 description explicitly states when to use (listing inbox emails) and when not to use (listing sent emails or broadcasts), and directs to alternative tools. This provides clear decision guidance.

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