clear_old_reminders

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'clear' implies a destructive operation, it doesn't specify whether this is reversible, what permissions are required, whether it affects only the user's reminders or shared ones, or what confirmation/feedback is provided. The description mentions 'completed/moved reminders' but doesn't clarify if both statuses are required or if it's an 'or' condition.

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 - a single phrase that communicates the core purpose without any wasted words. It's front-loaded with the essential information and contains no unnecessary elaboration.

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 destructive operation tool with no annotations and no output schema, the description is insufficient. It doesn't address important contextual aspects like what 'clear' actually means (permanent deletion? archiving?), what happens to the cleared items, whether there's confirmation or undo capability, or what the tool returns upon completion.

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?

Schema description coverage is 100%, with the single parameter 'days' well-documented in the schema. The description adds no additional parameter information beyond what's already in the schema, so it meets the baseline for adequate but not exceptional parameter 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 the action ('clear') and target ('old completed/moved reminders'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'delete_reminder' or 'complete_reminder' that might handle similar operations on individual 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?

No guidance is provided about when to use this tool versus alternatives like 'delete_reminder' or 'complete_reminder'. The description implies it's for batch operations on old items, but doesn't specify prerequisites, exclusions, or contextual triggers for choosing this over sibling tools.

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