list_emails

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

The description says 'List sent emails', but the schema includes a direction parameter with values 'inbound' and 'outbound', indicating the tool can list both. This contradicts the description, which incorrectly limits to sent only. No annotations exist to clarify behavior, so the description is misleading.

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 with two sentences: one for purpose and one for output fields. No extra words, but it could include the direction filter to avoid confusion.

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?

With 5 parameters and no output schema, the description omits critical context: the return structure, pagination use of 'after', and the fact that direction can filter inbound. It contradicts the available schema, leaving gaps for proper invocation.

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 input schema has 100% description coverage, so parameters are well-documented. The description adds minimal value beyond listing returned fields. The direction parameter's description in schema is detailed, but the tool description ignores it.

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 'List sent emails from the project's mailbox' with specific fields, making the purpose clear. It does not explicitly distinguish from siblings like list_mailbox_webhook_deliveries or get_email, but the action and resource are well-defined.

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 for listing sent emails but lacks explicit guidance on when to use alternatives or conditions like pagination. No exclusions or context for direction filter are mentioned.

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