Permanently remove a calendar event from iCloud Calendar using its calendar and event IDs. Set dry run to true to preview changes before deletion.
Delete a calendar event permanently from iCloud Calendar.
| Name | Required | Description | Default |
|---|---|---|---|
| dryRun | No | If true, report exactly what would change and do not modify anything | |
| eventId | Yes | Event ID to delete | |
| calendarId | Yes | Calendar ID containing the event |
Changes observed during successful MCP inspections.
v2.8.0Input schema / properties / dryRunAdded value: +{
+ "description": "If true, report exactly what would change and do not modify anything",
+ "type": "boolean"
+}v2.5.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It usefully discloses the irreversible nature ('permanently'), which is real behavioral value, but it omits authentication/permission requirements, iCloud sync behavior, and whether any confirmation or recovery exists.
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?
A single front-loaded sentence with the verb leading and zero filler. It is efficient and well-structured, though the extreme brevity leaves the information content thin.
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 keyed delete with complete parameter documentation and no output schema, the essentials are present. However, a permanent destructive operation with no annotations arguably warrants more than one sentence covering irreversibility, permissions, and how to preview via dryRun.
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 description coverage is 100%, including a clear dryRun explanation, so the schema already documents every parameter. The description adds no format or syntax detail beyond that, which matches the baseline of 3 when the schema does the heavy lifting.
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?
States a specific verb+resource: deleting a single calendar event, and adds platform scope ('from iCloud Calendar') plus permanence. An agent can readily distinguish it from delete_calendar or delete_reminder, though it never explicitly contrasts with the sibling bulk_delete_events.
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 gives no when-to-use guidance, no prerequisites, and no alternatives. It never tells the agent when to prefer this over bulk_delete_events for a single item or how it relates to get_event/list_events. Usage must be entirely inferred.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.