List follow-up reminders that are due now

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

No annotations are provided, so the description carries full burden. It discloses that the tool refreshes thread state and returns full context, but does not clarify whether state modification occurs or the exact nature of 'refresh'. The guideline about not calling followup_send without approval is helpful but not a behavioral trait of the tool itself.

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 three sentences long and front-loaded with core functionality. The third sentence about sending is somewhat tangential but still concise.

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 lack of annotations and output schema, and two undocumented parameters, the description is incomplete. It fails to clarify parameter usage or differentiate from the sibling 'followup_due', though it covers the main purpose.

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 two parameters (accountAlias, chatScope) with no description and 0% schema coverage. The tool description does not explain what these parameters represent or how to use them, leaving the agent without guidance.

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 due reminders and refreshes thread state. However, it does not differentiate from the sibling tool 'followup_due', which likely serves a similar purpose without multi-account support.

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 provides guidelines for the follow-up send action but does not specify when to use this tool over alternatives like 'followup_due' or 'multi_gmail_followup_cleanup'. No context on prerequisites or exclusions.

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