calendar_delete_event

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

The description adds value beyond the annotations by explicitly stating that the deletion is permanent, that attendees are notified of cancellation, and that the return value is JSON confirming deletion. This is meaningful behavioral context beyond the destructiveHint and idempotentHint flags.

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 two terse sentences with no filler. The primary purpose and the most important side effect are front-loaded, and the return note is cleanly separated.

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, destructive, idempotent delete operation, the description covers the permanent nature, the attendee notification side effect, and the return shape. The schema documents the parameters, and annotations cover the safety profile. No material gaps remain.

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 description itself contributes no parameter-specific guidance, but the schema provides clear descriptions for both parameters: event_id is 'The event ID to delete' and calendar_id is 'Calendar ID, or primary for the main calendar.' Since the schema covers parameter meaning, the baseline score applies.

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 action ('Permanently delete'), a specific resource ('a calendar event'), and a key consequence ('attendees are notified of cancellation'). This clearly differentiates it from siblings like calendar_create_event and calendar_update_event.

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 use case is implied by the verb 'delete' and the sibling list: use this when you need to remove a calendar event. However, there is no explicit when-to-use, when-not-to-use, or comparison to alternatives such as calendar_update_event.

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