hey_list_set_aside

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

With no annotations, the description carries the full burden. It discloses the caching mechanism and the option to force refresh, which is useful. However, it omits details about what 'Set Aside' means or what the returned data looks like, limiting transparency.

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 concise sentences front-load the core purpose and key behavior. No wasted words; every sentence serves a purpose.

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 one parameter and no output schema, the description is adequate but incomplete. It does not explain the concept of 'Set Aside' or specify the return format, which an agent might need to infer.

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 schema covers the single parameter force_refresh fully (100% description coverage). The tool description essentially repeats the same info, adding little value beyond reinforcing the caching behavior.

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 lists emails in the Set Aside stack, providing a specific verb and resource. However, it does not differentiate from sibling list tools like hey_list_imbox or hey_list_spam beyond the name.

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 explains the caching behavior and the force_refresh parameter, guiding when to bypass cache. But it offers no guidance on when to use this tool versus alternatives like hey_list_imbox or hey_set_aside.

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