delete_event

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

No annotations are provided, so the description carries full burden. It discloses the critical behavioral trait that deletion is 'permanent', which distinguishes it from trash/archive patterns. However, it lacks details about authorization requirements, side effects on event attendees, or reversibility windows.

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?

Single sentence with zero waste. 'Permanently' efficiently conveys destructiveness without extra words, and 'iCloud Calendar' front-loads the domain context immediately. Every word earns its place.

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 straightforward 2-parameter deletion tool without output schema, the description adequately covers the essential safety context (permanence) and system boundary (iCloud). Could be improved by noting where to obtain the IDs (e.g., from list_events), but sufficient for correct invocation.

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% with clear descriptions for calendarId and eventId. The description does not add parameter-specific guidance (such as ID formats or source locations), but with complete schema coverage, no additional compensation is required.

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 uses specific verb 'Delete' with resource 'calendar event' and specifies 'permanently from iCloud Calendar'. This clearly distinguishes it from sibling delete_email and distinguishes from update_event/create_event by explicitly stating the destructive action and target system.

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 word 'permanently' implies this is for irreversible removal, suggesting when to use it versus update_event, but lacks explicit when-to-use guidance or named alternatives (e.g., does not mention using update_event for modifications instead of deletion).

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