calendar_deleteEvent

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

The description only says 'Deletes an event' without disclosing that deletion is permanent, whether it requires special permissions, or what response to expect. Since no annotations are provided, the description carries the full burden but fails to add behavioral detail beyond the bare action.

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 concise sentence that directly states the tool's purpose without unnecessary words. It is front-loaded and easy to parse, though it sacrifices behavioral detail for brevity.

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?

As a destructive tool with no annotations and no output schema, the description is too thin to be fully actionable. It lacks information about the permanence of deletion, error conditions, and how the calendarId optionality works in practice, making it incomplete for an agent to use confidently.

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 input schema fully describes both eventId and calendarId (100% coverage), so the description does not need to repeat them. The description adds no additional parameter semantics beyond what the schema already provides, so a baseline of 3 is appropriate.

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 clearly states the action ('Deletes an event') and the resource ('from a calendar'), with a specific verb and direct object. This distinguishes it from sibling tools like calendar_getEvent or calendar_updateEvent, which have different actions.

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?

No guidance is provided on when to use this tool versus alternatives, such as how to obtain an eventId or that calendarId defaults to primary. The description simply states the operation, leaving the agent without context for integration.

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