delete-calendar-event

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

Annotations already indicate destructiveness (destructiveHint=true). The description adds important side effects: cancellation emails for meetings and the all-or-nothing behavior for series. No contradiction with annotations.

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?

Two sentences plus a tip, front-loaded with the core action. Every sentence adds meaningful information without unnecessary verbosity.

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 destructive tool with no output schema, the description covers the primary behavior and side effects well. It does not address permissions or non-meeting scenarios, but annotations partially fill that gap.

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 coverage is 100% with descriptions for all 4 parameters. The description adds value by relating the eventId to instance IDs from list-calendar-event-instances, but does not elaborate on other parameters like If-Match.

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?

Clearly specifies the action 'removes' and the resource 'event from the containing calendar'. The description also covers special cases (meetings, seriesMaster) which distinguishes it from siblings like delete-specific-calendar-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?

Provides a useful tip explaining that deleting a seriesMaster removes all occurrences and advises using list-calendar-event-instances for single instances. However, it does not explicitly state when to prefer this tool over other deletion tools like cancel-calendar-event.

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