Cancel a calendar event you organize and notify attendees with an optional cancellation message. Use it to remove meetings and keep participants informed.
Cancel a calendar event you organize and notify attendees
| Name | Required | Description | Default |
|---|---|---|---|
| comment | No | Cancellation message to attendees | |
| eventId | Yes | Event ID |
Changes observed during successful MCP inspections.
v1.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare destructive=true, openWorldHint=true, and idempotentHint=false, so the safety profile is clear. The description adds useful behavioral context by stating the caller must organize the event and that attendees are notified, going beyond the annotations without contradicting them.
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 a single focused sentence with the action and key constraints front-loaded. There is no redundant or filler text.
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 cancellation tool with full schema coverage and annotations covering destructive behavior, the description provides enough context to invoke it correctly. The main remaining gap is lack of explicit differentiation from sibling calendar deletion/decline tools.
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 100%, and both parameters are documented in the input schema, so the description does not need to repeat parameter details. It adds only light context by implying that attendee notification relates to the optional comment, but the schema already carries the substantive parameter semantics.
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 gives a specific verb and resource: cancel a calendar event. It also scopes the action to events the caller organizes and notes attendee notification, though it does not clearly distinguish cancel from sibling operations such as m365_calendar_delete or m365_calendar_decline.
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?
Usage is implied by the phrase 'calendar event you organize,' which suggests the prerequisite and intended scenario. However, the description does not explicitly say when to prefer cancel over delete or decline, nor does it state what to do if the caller is not the organizer.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.