update-specific-calendar-event

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

The description adds the warning about attendees replacing the entire list, which is a behavioral trait not covered by annotations (destructiveHint=true already indicates mutation). However, it does not disclose other important behaviors like partial vs full updates or read-only fields.

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 two sentences plus a tip and warning. The purpose is stated first, followed by critical usage details. It is appropriately front-loaded and each sentence adds value.

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 covers the critical point about attendees and email addresses, which is helpful given the complex nested schema. However, it lacks details on overall update behavior (partial vs full replacement for fields other than attendees), and does not reference read-only fields from the schema.

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 80%, so the baseline is 3. The description adds context for the 'attendees' parameter via the tip and warning, but does not explain other parameters beyond what the schema 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 states 'Update the navigation property events in me' which is vague and does not clearly indicate that this tool updates a specific calendar event. The tool name is clear, but the description lacks specificity and does not differentiate from sibling tools like 'update-calendar-event'.

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 about using list-users to find email addresses and a warning about attendees replacing the entire list. This provides clear context for handling attendees. However, it does not explicitly state when to use this tool versus similar update tools.

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