calendar_delete_event

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

Discloses irreversibility, platform limitation for recurring events, and that the tool returns PLATFORM_LIMITATION instead of false success. This goes beyond the destructiveHint annotation.

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?

Concise and well-structured. Front-loaded with [IRREVERSIBLE] warning, followed by purpose, limitation, and requirement. Every 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?

Covers key behaviors: irreversible, confirmation needed, recurring event handling, and platform limitation. No output schema, but description adequately explains expected outcomes.

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?

Adds value beyond schema by explaining that confirm must be true, and providing guidance on calendarName vs calendarIndex for disambiguation. Schema coverage is 50%, but the description compensates well.

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 clearly states the action: delete an event by uid. It distinguishes from sibling tools like calendar_delete_calendar by highlighting the recurring event limitation, which is specific to this tool.

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?

Explicitly states when to use (to delete a single event) and when not to (for recurring events, use Calendar.app). Also specifies requirement: confirm must be true.

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