fetch_emails

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

No annotations provided; description misses key behavioral traits like marking emails as read or network dependencies. Mentions auto-detection but not side effects.

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?

Well-structured with sections, though sample prompts add length. Every sentence adds value; front-loaded with provider info.

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?

Complex tool with 6 parameters and no explicit return value description despite having an output schema. Does not explain output format, leaving agent guessing.

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 has 0% description coverage, but description explains all 6 parameters in detail with examples for search. Compensates fully for schema gaps.

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 tool fetches emails via IMAP and lists supported providers. It distinguishes from diverse sibling tools like google_search or ocr_image.

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?

Provides sample prompts and provider-specific instructions (e.g., Gmail app passwords). Lacks explicit exclusions or when-not-to-use guidance, but context is clear.

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