hey_list_set_aside

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

Annotations already provide readOnlyHint and openWorldHint. The description adds caching behavior ('Returns cached results unless force_refresh=true'). No contradictions, but additional behavioral details like pagination or limits are missing.

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 sentences, no redundant words. Purpose and caching behavior are front-loaded. Every word earns its place.

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 simple schema (one optional boolean) and good annotations, the description covers the main behavior. It could mention sorting or limits, but not essential for a list tool.

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 explains the effect of the 'force_refresh' parameter beyond the schema's description, linking it to caching behavior. Schema coverage is 100%, so baseline is 3, and the description adds value.

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 it lists emails from the 'Set Aside' stack, with a specific verb ('List') and resource ('emails'). It distinguishes from sibling tools like 'hey_list_emails' and 'hey_list_collection_emails' by specifying the 'Set Aside stack'.

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 when to use (to list set aside emails) but provides no explicit guidance on when not to use or alternatives. Siblings are listed but not compared.

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