Delete Calendar Event

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

Beyond annotations (destructiveHint=true, readOnlyHint=false), the description adds critical behavioral context: always requires user confirmation, permanent deletion, attendee cancellation notices, and need for confirm parameter to be True.

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 efficient and well-structured: opens with a clear action, includes a warning, then lists parameters in a clean args block. No unnecessary sentences.

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 4 parameters, 2 required, destructive, and an output schema. The description covers purpose, irreversibility, attendee notices, parameter meanings, and return confirmation. Lacks mention of error handling or prerequisites but is sufficient for a delete 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?

Despite 0% schema description coverage, the description fully explains all 4 parameters with purpose and semantics (e.g., account_id as Microsoft account ID, event_id as the event to delete, send_cancellation default true, confirm must be True to prevent accidents).

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 tool deletes a calendar event, with a permanent irreversible action. This verb+resource combination is distinct from sibling tools like calendar_create_event, calendar_update_event, etc.

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 implies usage for deleting events and warns about permanence and attendee notifications, but does not explicitly state when to use this tool vs alternatives or provide exclusion criteria.

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