Overdue Reminders

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

The annotations already include readOnlyHint=true, indicating a safe read operation. The description adds behavioral context: it returns only 'incomplete' reminders that are 'due before today' and operates 'across all lists'. This enriches the agent's understanding beyond the annotations.

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 a single sentence with no redundant information. It directly states the tool's purpose, scope, and condition. Every word adds value, making it concise and well-structured.

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 tool's simplicity, the description explains the core functionality but omits details about the limit parameter and how results are ordered or paginated. Since an output schema exists, return values are covered, but the parameter behavior is missing, leaving minor gaps in completeness.

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 one optional parameter (limit) with 0% schema description coverage. The description does not mention or explain the limit parameter, leaving the agent without guidance on its semantics. The description fails to compensate for the lack of schema documentation.

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 'Return incomplete reminders due before today across all lists'. It specifies the verb 'Return', the resource 'incomplete reminders due before today', and the scope 'across all lists'. This clearly differentiates it from sibling tools like reminders_today (today's reminders) and reminders_list (all reminders).

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 its usage context (overdue reminders) but does not provide any guidance on when to use this tool versus alternatives like reminders_today or reminders_search. No exclusions or comparisons are mentioned, leaving the agent to infer the appropriate usage.

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