delete_event

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. It does so by explaining the destructive difference between deleting one occurrence versus the entire series. It doesn't mention permissions or irreversibility, but the verb 'delete' plus the series nuance covers the main risk.

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: the first states the action, the second provides the only necessary conditional guidance. No filler or repetition of schema details.

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 single-parameter delete tool with no output schema and no annotations, the description sufficiently covers the key scenario (recurring events) and the source of the ID is in the schema. Minor missing details like return value or explicit irreversibility are not critical given the tool's simplicity.

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% and the schema describes 'id' as 'the event ID to delete, as returned by search_events.' The description adds meaning by explaining that the same parameter can be an occurrence id or a master id, which is critical for recurring events and goes beyond the schema description.

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?

Description uses a specific verb and resource: 'Delete a calendar event.' The recurring-event clause clarifies the scope of deletion, distinguishing it from siblings like update_event (modification) and search_events (querying).

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 explicit operational guidance for recurring events: 'pass an occurrence id to cancel just that occurrence, or the master id to delete the entire series.' This tells the agent when to use which ID, though it doesn't explicitly list alternative tools for other use cases.

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