snooze-calendar-event-reminder

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

Annotations already indicate destructiveHint=true, so the description adds value by specifying that the reminder is postponed and will re-fire at the new time. It does not contradict annotations and provides behavioral context beyond what annotations encode. No mention of side effects or authorization requirements, but the core mutation behavior is clear.

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 with a tip, effectively conveying the purpose and parameter format. Minor redundancy ('postpone' and 'postpones') but overall concise and well-structured. It front-loads the key action and then adds parameter details.

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?

The description explains what the tool does and how to use the body parameter, but it does not mention return values (no output schema) or prerequisites like the event needing an existing reminder. It also doesn't note the openWorldHint annotation's implications. Adequate but with gaps that could confuse an agent.

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 coverage is high (75%), but the description explains the body structure with examples ({ NewReminderTime: { dateTime, timeZone } }) and clarifies the timeZone format ('Pacific Standard Time'), which adds meaning beyond the schema's generic descriptions. This helps the agent construct the correct body object.

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 'Postpone a reminder for an event in a user calendar until a new time', which is a specific verb+resource. It distinguishes itself from sibling tools like 'dismiss-calendar-event-reminder' (which stops reminders) and 'cancel-calendar-event' (which cancels the event), making the purpose unambiguous.

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 mentions 'Postpones a triggered event reminder', implying it is used for reminders that have already fired. However, it does not explicitly compare with alternatives like 'dismiss-calendar-event-reminder' or provide guidance on when to use this tool versus others. The tip adds some usage context but lacks explicit when-to-use and when-not-to-use instructions.

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