Delete Event

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

WARNING explicitly states permanent removal from all attendee calendars, which is critical destructive behavior. No annotations are provided, so the description carries the transparency burden; it covers the main side effect but does not mention error cases or idempotency.

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?

Three short sentences with a clear warning and required parameter; every sentence earns its place with no fluff.

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 single-parameter delete tool, the description covers the purpose, permanent effect, and required input. It omits return/error behavior, but with no output schema and a low-complexity operation, this is complete enough.

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 covers event_id with 100% coverage and description simply repeats 'Required: event_id', adding no extra meaning beyond the schema's 'The EventId to delete'.

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 uses specific verb 'Delete' and resource 'calendar event from Less Annoying CRM', clearly distinguishing from sibling tools like create_event, edit_event, and search_events.

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 explicit guidance on when to use this versus alternatives like edit_event or search_events. The context of deleting is implied but lacks exclusions or alternative mention.

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