Reset, snooze or change a gear reminder

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

With annotations already indicating a mutable, non-idempotent operation, the description adds useful behavioral context by explaining that reset starts counting again and presenting the three modes. It does not describe parameter exclusivity or side effects, but the annotations lower the burden and the description adds meaningful context.

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?

A single sentence conveys the essential operations and even adds a clarifying parenthetical for reset. No filler, no repetition of schema details, and the core action is front-loaded.

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 tool with 7 parameters and low schema coverage, the description omits important operational constraints: whether reset can be combined with new limits, whether snooze_days is exclusive with days, and what happens when no operation parameter is provided. The presence of an output schema helps but does not resolve these gaps.

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 only 29%, so the description must compensate. It maps reset to 'starts counting again', snooze to 'snooze it', and change to 'change its limits', but it does not explicitly map days, distance_km, or name to those limits. The grouping is helpful but leaves ambiguity.

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 names a specific verb ('Reset... snooze... change') and a specific resource ('a gear reminder'), and clarifies the three distinct operations the tool performs. It clearly differentiates from the sibling add_gear_reminder by addressing existing reminders rather than creation.

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 gives concrete context for when to use the tool, particularly for resetting after maintenance, snoozing, or changing limits. It does not explicitly exclude add_gear_reminder for new reminders or describe when snoozing is preferable to changing limits, but the intent is clear.

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