Delete or cancel a calendar event by providing its event ID. Resolves the need to remove unwanted or duplicate events from Google Calendar.
Elimina o cancela un evento del calendario usando su ID.
| Name | Required | Description | Default |
|---|---|---|---|
| eventId | Yes | ID del evento a eliminar |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description carries the full burden of behavioral disclosure. It only restates the destructive action and does not disclose consequences, reversibility, or failure behavior.
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 with no redundant content. It is appropriately concise, though minimal.
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 one-parameter destructive tool, the description conveys the basic call mechanism. However, it lacks notes on outcome, side effects, or delete-versus-cancel semantics, leaving completeness partial.
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 description coverage is 100%, and the description only repeats 'usando su ID'. It adds no meaningful semantic detail beyond the schema's eventId field.
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 action: eliminating or cancelling a calendar event by its ID. This distinguishes it from siblings such as create_event, list_events, and reschedule_event.
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 given about when to choose this tool over alternatives or about any prerequisites. The intended use is inferable from the action, but no explicit exclusions or alternative recommendations are provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.