calendar_delete_event

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

With no annotations, the description carries a heavier burden. It discloses a key behavioral consequence (attendees will be notified of cancellation) and the confirm requirement, but it does not mention whether deletion is permanent, how it affects recurring events, or what happens if confirm is false. Partial disclosure only.

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 description is two sentences: the first states the purpose, the second explains the confirm requirement. It is front-loaded, concise, and every sentence earns its place with no redundancy.

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?

Given the absence of annotations and output schema, the description is arguably minimal for a delete operation. It covers the essential confirm behavior but omits important operational details such as permanence, error conditions, and what the response contains. Still, it's better than nothing, earning a middle score.

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% for all four parameters, so the baseline is 3. The description adds meaning beyond the schema by explaining why confirm is needed ('since they will be notified of the cancellation'), providing additional context for the confirm parameter that the schema only hints at.

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 'Delete a Google Calendar event,' which clearly identifies the verb (delete) and resource (Google Calendar event). It distinguishes from sibling tools like calendar_update_event and calendar_create_event, and adds a critical condition about the confirm flag for events with attendees.

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 clearly implies when to use this tool (when deleting an event) and provides specific guidance about the confirm parameter for events with attendees. It doesn't explicitly mention alternatives or exclusions, but the context is sufficient for an agent to select this tool over siblings.

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