read_inbox

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

Despite no annotations, the description provides a comprehensive 'Behavioral Transparency' section covering side effects (read-only, no side effects), authentication, rate limits, error handling, idempotency, and data privacy. This fully informs the agent of behavioral traits.

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 lengthy with structured sections, but some parts (e.g., 'When to use' reads like a generic template) add redundancy. While well-organized, it could be more concise by removing generic statements and focusing on email-specific details.

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, the description adequately explains return format and behavior. However, it omits details about pagination or handling large folders, and the missing api_key parameter explanation reduces completeness. Error handling and rate limits are covered well.

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 0%, so the description must explain parameters. The 'Args' section explains folder and limit (defaults and max), but does not mention the api_key parameter present in the schema. This omission leaves ambiguity about how authentication is handled via parameter vs environment variable.

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 that it reads recent emails from a mailbox folder and returns subject, from, date, and body preview. This distinguishes it from sibling tools like create_draft, list_folders, search_emails, and send_email.

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 includes 'When to use' and 'When NOT to use' sections, but the content is generic ('structured analysis or classification') and not specific to reading emails. It lacks explicit differentiation from siblings or clear guidance on when to use this tool versus search_emails or others.

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