delete_event

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It discloses the delete_repeats option, which clarifies default behavior, but it does not mention whether deletion is permanent, if special permissions are required, or what happens to related attendee data. This is a significant gap for a destructive operation.

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 concise sentences with a front-loaded purpose statement and a clear instruction. No unnecessary words, making it easy to parse quickly.

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 2-parameter tool with no output schema or annotations, the description covers the core function and the key option. However, it lacks important context such as permanence of deletion, permission requirements, or behavior for events that have already occurred, leaving some gaps.

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 schema only describes delete_repeats, not event_ids. The description adds value by clarifying that event_ids refer to calendar events, partially compensating for the gap. However, it does not add semantics beyond what the schema already provides for delete_repeats, so the contribution is moderate.

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 clearly states the verb 'Delete' and resource 'calendar events', distinguishing it from sibling tools like update_event or create_calendar_event. It also specifies that multiple events can be deleted at once and mentions the delete_repeats option, making the scope explicit.

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 provides clear context for when to use this tool: whenever you need to delete calendar events. It also gives a specific instruction for handling repeat instances (set delete_repeats=true), but does not explicitly reference alternative tools or exclusions. This is clear context without exclusions, aligning with the 4-level.

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