update-calendar-event

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

The description discloses the important behavior that setting attendees replaces the entire list, which adds value beyond annotations (destructiveHint=true, openWorldHint=true). No contradictions with annotations. However, it could mention more side effects like permissions or irreversible actions.

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 concise with a clear purpose and a tip, but the tip is somewhat lengthy and could be shortened. It is 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?

Given the complex input schema (many nested objects) and no output schema, the description is too sparse. It does not explain the return value, common use cases, or constraints. Annotations provide some context, but more detail would improve completeness.

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 coverage is 75%, and the description adds no parameter-specific information beyond what the schema already provides. The baseline is 3, and the description does not exceed that.

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 and resource. However, it does not differentiate from similar sibling tools like update-specific-calendar-event or update-calendar, so it loses a point for lacking sibling 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?

The description includes a critical tip advising against guessing email addresses and recommends using list-users tool, plus a warning that attendees replacement is wholesale. This provides clear when-to-use and what-to-avoid guidance, though it does not compare to alternative tools.

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