delete_event

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

The description adds minimal behavioral context beyond the annotations. The term 'cancel' hints at calendar-specific semantics (such as notifying attendees) compared to plain 'delete', but it does not elaborate on side effects, permanence, or idempotency. The annotations already declare destructiveHint=true, so the description is not required to repeat safety, but it falls short of providing richer context.

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 a single, focused sentence with no filler or redundant wording. It is front-loaded and efficient.

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 one-parameter destructive action with annotations covering the safety profile, the description is minimally adequate. However, it lacks information about the distinction between delete and cancel, potential consequences (e.g., notifications to attendees), and reversibility, which would be valuable for a destructive calendar operation.

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 event_id parameter is not described at all in the description, and schema_description_coverage is 0%. The parameter name is self-explanatory, but the description fails to clarify format, requiredness, or semantics beyond the name, leaving the agent without supportive context.

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 a specific action ('delete/cancel') on a specific resource ('calendar event'), distinguishing it from sibling delete tools for folders or messages. The verb is unambiguous and the resource is 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 no guidance on when to use this tool versus alternatives like update_event or respond_event. It does not mention scenarios, prerequisites, or exclusions.

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