update-calendar-event

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

The description adds value beyond annotations by warning about attendee list replacement. However, it does not disclose other behavioral traits such as permission requirements, rate limits, or whether the update is partial or full replacement. Annotations already mark destructiveHint=true, so the description adds moderate context.

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 short (two sentences plus tip/warning) and front-loaded with the main purpose. It is efficient with no fluff, though the structure could be improved with a more formal layout.

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?

Given the tool's complexity (5 params, nested objects, destructive nature) and no output schema, the description covers some behavioral aspects (attendees replacement) but lacks information on return values, error handling, or confirmation gate behavior. It is reasonable but incomplete.

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 schema description coverage at 80%, the schema already documents most parameters in detail. The description does not add any new information about parameters beyond what the schema provides, hence baseline 3.

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 'Update the properties of the event object', which is a specific verb ('Update') and resource ('event object'). However, it does not differentiate this tool from its sibling 'update-specific-calendar-event', which updates events in a specific calendar rather than the default calendar.

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 provides explicit guidance: do not guess email addresses (use list-users tool) and warns that setting attendees replaces the entire list. It lacks explicit when-to-use vs. alternatives, but the tip and warning are helpful for correct usage.

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