List follow-up reminders that are due now

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

No annotations provided, so description carries the burden. It mentions 'refresh thread state' (mutation) and returns full context, but does not disclose side effects like whether reminders are marked as seen or if state changes are permanent.

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?

Three sentences with front-loaded purpose and key usage guidelines. No superfluous text, but slightly more detail could be added without harming conciseness.

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?

No output schema, no annotations, and parameter semantics missing. The description covers purpose and usage but lacks prerequisites, parameter meaning, and expected output format. For a tool interacting with email state, more context is needed.

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?

Description does not mention the two parameters (accountAlias, chatScope). Schema description coverage is 0%, and no parameter details are added, leaving the agent without guidance on how to set these fields.

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 reminders due now, refreshes thread state, and returns full thread context. It distinguishes from siblings like followup_trigger and followup_send by focusing on listing due reminders for review.

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?

Explicitly instructs to present drafts for proof-reading before sending and never call followup_send without approval. This provides clear when-to-use and when-not-to-use guidance beyond just the tool function.

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