read_emails

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

No annotations are provided, so the description carries the full burden. It discloses that the tool fetches 'recent emails' and handles pagination via 'page_token', which adds useful behavioral context. However, it lacks details on permissions, rate limits, or error handling, which are important for a tool interacting with an external service like Gmail.

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 well-structured and concise, with a clear purpose statement followed by 'Args:' and 'Returns:' sections. Each sentence adds value without redundancy, making it easy to scan and understand the tool's functionality and outputs efficiently.

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 the tool's moderate complexity (2 parameters, no annotations, but with an output schema), the description is fairly complete. It explains the purpose, parameters, and return values. The output schema is mentioned, so detailed return value explanations aren't needed. However, it could improve by addressing authentication or error scenarios.

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?

The description adds meaningful semantics for both parameters: 'max_results' is explained as 'Number of emails to fetch,' and 'page_token' as 'Optional page token to fetch next batch.' This compensates for the 0% schema description coverage by clarifying the purpose and usage of each parameter beyond their types and defaults.

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's purpose: 'Fetch recent emails from Gmail inbox.' It specifies the verb ('fetch') and resource ('emails from Gmail inbox'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate from sibling tools like 'create_new_email_draft' or 'create_reply_draft', which are write operations, whereas this is a read operation.

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 implies usage through the context of fetching emails, but it doesn't explicitly state when to use this tool versus alternatives. There are no guidelines on prerequisites, such as authentication or access rights, or exclusions. The presence of sibling tools suggests potential alternatives, but no direct comparison is provided.

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