hey_list_collection_emails

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

The description mentions caching behavior and the force_refresh parameter, which adds transparency beyond a basic read operation. However, no annotations are provided, and the description does not cover other behavioral aspects like pagination limits or rate limits.

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?

Two short sentences that are front-loaded with the core purpose and immediately add valuable behavioral context about caching. No filler or redundancy.

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?

For a simple list tool with no output schema, the description provides basic functionality and a key behavioral note (caching). However, it lacks details on return format, error handling, or pagination nuances, which could be helpful given the absence of an output schema.

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?

All 4 parameters have descriptions in the input schema, achieving 100% coverage. The description does not add additional meaning beyond what is already in the schema, such as format constraints or default values.

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 action ('List emails') and the resource ('in a specific collection'), distinguishing it from sibling tools like 'hey_list_imbox' or 'hey_list_drafts' which target different email groupings.

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 explicit guidance on when to use this tool versus alternatives. The purpose is implied by the name, but the description does not discuss exclusions or alternative tools for different contexts.

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