Update the weekly availability schedule for a calendar. This replaces all existing slots.
| Name | Required | Description | Default |
|---|---|---|---|
| slots | Yes | Array of availability slots | |
| calendarId | Yes | The calendar ID |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description states 'This replaces all existing slots,' which is a destructive behavior, but the annotation destructiveHint=false. This directly contradicts the annotation. Therefore, despite the useful disclosure, the contradiction forces a score of 1.
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 short sentences, with the key replacement behavior disclosed in the second sentence. The description is front-loaded and contains no redundant information.
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 simple two-parameter tool with full schema coverage, the description covers the essential purpose and the critical replacement behavior. However, it does not address openWorldHint implications or provide usage context, and the contradiction with destructiveHint is a notable gap.
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?
The input schema provides 100% coverage for both parameters (calendarId and slots), including detailed descriptions for the slot object fields. The description adds no additional parameter semantics beyond what the schema already documents, so the baseline 3 applies.
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 updates the weekly availability schedule for a calendar, with a specific verb and resource. It also explicitly notes that it replaces all existing slots, distinguishing it from read-only siblings like get_calendar_weekly_availability.
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 updating weekly availability, but provides no explicit when-to-use guidance or alternatives. It does not contrast with related tools like update_calendar or create_calendar_override.
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.
