delete_event

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

With no annotations provided, the description must convey behavioral traits, but it only states the action 'Delete' without disclosing permanence, irreversibility, authorization requirements, or what happens to related data. The word 'delete' implies destruction, but the description fails to add useful context beyond the operation itself.

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, front-loaded sentence that immediately conveys the action and target. There is zero wasted text, and for such a simple operation, this level of conciseness is appropriate.

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?

The tool has only one parameter and no output schema, but it is a destructive mutation with no annotations, so the description should at minimum note permanence or the result of a successful deletion. It does not, leaving the agent without important contextual information about consequences or return values.

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 already provides 100% coverage with a clear description of the 'id' parameter as 'The event UUID', so the description adds no parameter-specific meaning. Per the rubric, this high schema coverage warrants a baseline score of 3.

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 ('a calendar event'), which distinguishes it from create/update/get operations on events. However, it is essentially a rewording of the tool name and adds no additional detail about scope or behavior beyond the obvious action.

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, such as get_event or update_event for modifying rather than removing an event. There are no exclusions, prerequisites, or notes about permanent deletion, so the agent receives no contextual instructions.

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