Delete iCloud Event

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

Annotations provide destructiveHint=true, but the description adds important behavioral context by warning that the action is destructive and requiring user confirmation. This goes beyond what annotations alone convey, ensuring the agent acts cautiously.

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 extremely concise with only three sentences: a one-line purpose, a parameter list, and a behavioral note. Every sentence serves a distinct purpose with no redundancy, making it easy to parse quickly.

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 delete tool with only 2 parameters and no output schema, the description covers the essential purpose, parameters, and behavioral warning. No additional context is necessary 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?

The input schema covers 100% of parameters, so the description need not repeat everything. However, it adds value by clarifying that the 'calendar' parameter accepts a 'Display name or full CalDAV URL', which provides practical usage detail beyond the schema's generic description.

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 explicitly states 'Delete an event by UID', clearly indicating the verb (delete) and resource (event). This distinguishes it from sibling tools like icloud_create_event, icloud_update_event, and icloud_list_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 includes 'This is destructive. Confirm with the user before invoking.', providing clear context on when to use the tool (after user confirmation). It does not explicitly mention when not to use it or alternatives, but for a delete operation, the guidance is adequate.

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