Create an availability override for a specific date (e.g., block a day off or modify hours).
| Name | Required | Description | Default |
|---|---|---|---|
| date | Yes | Date in YYYY-MM-DD format | |
| reason | No | Reason for the override | |
| endTime | No | Override end time in HH:mm format (if not blocked) | |
| isBlocked | Yes | If true, entire day is blocked | |
| startTime | No | Override start time in HH:mm format (if not blocked) | |
| calendarId | Yes | The calendar ID |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations show this is a non-read-only, non-destructive operation. The description adds the key behavioral distinction between blocking a day and modifying hours, but does not disclose edge cases like what happens when an override already exists for the date or permission requirements.
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 that fully captures the core action and use cases. No redundant wording or filler.
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 create operation with 6 parameters and no output schema, the description covers the essential purpose and examples. It is slightly incomplete regarding preconditions (e.g., whether an override on the same date is replaced) and success behavior, but schema and annotations cover most of the remaining context.
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%, so parameters are fully documented. The description adds no new parameter-level details beyond the schema, but the examples ('block a day off or modify hours') map to the isBlocked, startTime, and endTime parameters, providing a minor semantic cue.
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 creates an availability override for a specific date, with concrete examples (block a day off or modify hours). This distinguishes it from sibling tools like delete_calendar_override or get_calendar_overrides.
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 usage for date-specific availability changes but does not explicitly mention when to use this over alternatives such as update_calendar_weekly_availability or delete_calendar_override. No exclusions or alternative tool references are provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools are clearly distinct, but update_calendar overlaps with specialized tools like update_booking_settings, update_confirmation_settings, and the reminder management tools (add/delete/get reminders). This creates ambiguity about which tool to use for modifying specific settings such as buffers or reminders, though descriptions help clarify the intended scope.
All 28 tools follow a consistent verb_noun snake_case pattern (e.g., create_calendar, get_appointments, update_contact). The verbs are predictable (add, cancel, create, delete, get, reschedule, send, update), making the API easy to navigate.
With 28 tools, the set exceeds the 25+ threshold typically considered too many. While each tool serves a legitimate purpose, the high number is overwhelming and likely includes more granularity than necessary; some settings tools could be consolidated.
The tool surface covers the full lifecycle of calendars, appointments, and contacts, including availability, overrides, reminders, confirmation settings, and notifications. There are no obvious dead ends or missing operations; cancellation and rescheduling handle appointment changes, and send_invitation covers creation.
