cancel-calendar-event

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

Discloses that it moves event to Deleted Items, requires organizer, sends custom message, errors for attendees, and distinguishes from Delete. No contradiction with annotations (destructiveHint=true, readOnlyHint=false).

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?

Well-structured with clear sections, but slightly verbose. The tip is helpful but adds extra length. Still, every sentence adds value.

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?

Covers behavior, error cases, role requirements, and alternatives. No output schema, but description indicates outcome (cancellation message sent, event moved). Sufficient for agent to understand tool's effect.

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?

Description explains the body parameter (Comment field) and the eventId for recurring events. It adds meaning beyond schema. However, includeHeaders and excludeResponse are not described, though schema coverage is high.

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 it cancels a calendar event, requires organizer role, and sends cancellation message. It differentiates from delete-calendar-event and decline-calendar-event, making its purpose distinct.

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?

Explicitly states when to use (organizer wants to cancel and notify attendees), when not to use (attendees should use decline), and provides alternative (delete-calendar-event). The tip reinforces usage distinction.

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