snooze-calendar-event-reminder

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

Beyond the destructiveHint annotation, the description adds that the reminder 'will re-fire at the new time', explaining the behavioral consequence. It does not contradict annotations (readOnlyHint=false, destructiveHint=true).

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?

Two sentences: first states purpose, second provides a tip with body format. No wasted words. Front-loaded with the core action.

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?

Lacks description of return values (no output schema), prerequisites (e.g., event must have an active reminder), and whether the operation is reversible. Given the tool's mutability (destructiveHint=true) and no output schema, more context is needed for an agent to invoke correctly.

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?

With 75% schema coverage, the description adds value by specifying that dateTime must be ISO 8601 and timeZone can be IANA or Windows (e.g., 'Pacific Standard Time'), which is more explicit than the schema's examples. However, it does not cover eventId or includeHeaders/excludeResponse, but those are well-described in the schema.

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 'Postpone a reminder for an event in a user calendar until a new time.' The verb 'postpone' combined with 'reminder' and the specific body structure distinguishes it from similar siblings like 'dismiss-calendar-event-reminder'.

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 that this tool is for triggered reminders ('Postpones a triggered event reminder') but does not explicitly state when to use it versus alternatives like 'dismiss-calendar-event-reminder'. No guidance on prerequisites or exclusions is provided.

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