update-specific-calendar-event

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

The description adds a valuable behavioral warning: 'Setting attendees replaces the entire attendee list — include all attendees, not just new ones.' The annotations already mark the tool as destructive (destructiveHint: true) and the description's 'Update' aligns with that. No contradiction exists. This warning provides context beyond annotations, though other side effects (e.g., what happens to omitted fields) are not addressed.

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 front-loaded with the core purpose ('Update a specific calendar event') and includes only two additional sentences. Both the tip about list-users and the warning about attendees are critical and earn their place. It is concise and well-structured.

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 is minimal, but the schema and annotations provide substantial context (e.g., required parameters, destructiveHint). However, it does not clarify the difference from 'update-calendar-event' or the confirmation behavior (the confirm parameter is described in the schema but not the description). Given the tool's complexity and the absence of an output schema, the description could be more complete.

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 schema has 83% description coverage, so the baseline is 3. The description adds a tip about using list-users to find email addresses (relevant to the attendees parameter) and warns about attendee replacement, but it does not explain the body structure, confirm parameter, or other semantics beyond what the schema already provides.

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 action ('Update a specific calendar event') with a specific verb and resource. However, it doesn't explicitly differentiate from the sibling tool 'update-calendar-event', relying on the name 'specific' and the presence of calendarId/eventId parameters to imply that distinction.

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?

No guidance is provided on when to use this tool versus the similarly named 'update-calendar-event' or other calendar update tools. The only cross-tool reference is 'Use the list-users tool to find the email address', which is an operational tip for a sub-task, not a usage guideline for the tool itself.

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