Delete event

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety bar is lower. The description still earns credit by adding that the action cannot be undone, that a recurring event's entire series is removed, and that admin privileges are required — all behavior not encoded in the structured fields.

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 destructive scope and irreversibility are front-loaded, which is good. However, 'Admins only' appears twice (opening line and closing line), wasting a sentence in an otherwise very short description.

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 two-parameter destructive tool with full schema coverage, complete annotations, and no output schema, the description covers the essentials an agent needs: permissions, irreversibility, and recurring-series blast radius. Only the single-occurrence case and post-delete response are left implicit.

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 both parameters fully documented (group URL name, event_id from list_events), so baseline 3 applies. The description adds only the notion of targeting a single event and says nothing about resolving recurring instances or what event_id format is expected beyond the schema.

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 verb and resource ('Delete a calendar event') with an access constraint, which separates it cleanly from the many other delete_* siblings (delete_post, delete_group_link, delete_category). It never explicitly contrasts with update_event or list_events, but the destructive action is unambiguous.

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?

Adds useful context that it is equivalent to the event's Delete button in the Calendar tab, and that admins are the only permitted callers. It does not say when to prefer update_event or how to handle the recurring-series case if only one occurrence should go, so the agent must infer guidance.

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