Delete an event

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

Beyond the destructiveHint annotation, the description reveals the permanence (no undelete), the side effect on all guests, the conditional email behavior, and the return payload {deleted:true}. It fully discloses what happens at the domain level.

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?

Three dense sentences front-load the most important warning (no undelete) and then cover series semantics, guest impact, email behavior, and return value without any filler. Every sentence 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 destructive, non-idempotent operation with no output schema, the description covers the outcome, return value, recurrence nuances, and email side-effect. The schema covers the remaining parameter details, so nothing essential is missing.

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?

Even though the schema already documents all parameters, the description adds critical meaning: it explains which event_id form affects the whole series versus one occurrence, and it emphasizes that attendees are not notified unless send_updates=all, reinforcing the default. This materially helps an agent choose the right parameter values.

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 opens with a precise verb and resource — "Deletes (cancels) an event" — and immediately distinguishes recurring-series deletion from single-instance deletion by naming list_event_instances. This clearly separates it from siblings like update_event, move_event, and create_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 description gives concrete selection guidance: pass the series master id to cancel the entire series, or an instance id from list_event_instances to cancel only one occurrence. It also clarifies the send_updates option's effect on notification emails, though it does not explicitly contrast delete with non-destructive alternatives.

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