list_emails

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

No annotations exist, and the description does not disclose behavioral traits like authentication requirements, whether the operation is read-only, pagination behavior, or return format. The agent is left uninformed about side effects or constraints.

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?

At six words, the description is extremely concise, but this brevity sacrifices critical information. It does not earn its place as every sentence should; it is under-specified rather than efficiently informative.

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 opaque parameter schema, no annotations, many sibling tools, and an existing output schema not described, the description fails to provide enough context for correct invocation. It lacks details on folder identification, filtering, pagination, or output structure.

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 only parameter is 'kwargs' of type object, with no schema-level descriptions and 0% coverage. The description fails to explain what keys or values this parameter should contain, leaving the agent without guidance on how to construct the argument.

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 'List emails in a folder' clearly states the action and resource, but lacks specificity about which folder or what subset of emails (e.g., all, recent, filtered). It does not distinguish from sibling tools like 'search_emails' which also deal with listing 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?

No guidance is provided on when to use this tool versus alternatives such as 'search_emails', 'get_email', or 'list_folders'. The agent has no context on prerequisites or exclusions.

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