hey_list_reply_later

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds useful context about caching behavior ('Returns cached results unless force_refresh=true'), which goes beyond the annotations and helps the agent understand response timeliness.

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 extremely concise, consisting of two sentences with no filler. The main action ('List emails in the Reply Later stack') is front-loaded, and every sentence adds value.

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 adequately covers the operation and parameter behavior. It could optionally mention the structure of returned emails, but the sibling tools likely share a similar return format, and the agent can infer from context.

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% coverage with a clear description for the sole parameter 'force_refresh'. The description merely restates the effect of the parameter, providing no additional semantic information beyond what the schema already conveys.

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 'Reply Later' stack, using a specific verb and resource. It distinguishes itself from sibling list tools (e.g., hey_list_emails, hey_list_screener) by targeting a particular stack, and also mentions caching behavior.

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 this tool (to list Reply Later emails) and provides a condition for refreshing cache (force_refresh=true). However, it does not explicitly exclude other use cases or compare with alternatives like hey_list_collection_emails.

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