Cancel booking

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

Annotations already carry destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered. The description still adds real value beyond them: the calendar event is removed, cancellation notifications are sent according to the page's settings, and confirmation is required first — side effects an agent cannot infer from the hints alone.

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?

Two sentences, front-loaded with the action and actor, followed by the consequences and the confirmation requirement. Every clause earns its place with no padding.

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 with no output schema, the description covers actor scope, side effects (event removal, notifications), and a confirmation safeguard. It leaves only minor gaps, such as behavior when the booking is already cancelled (implied by idempotentHint=true but not stated).

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?

With a single parameter at 100% schema description coverage, the schema already documents bookingId fully, including its provenance (search_bookings or list_upcoming_bookings). The description adds no parameter-level meaning, so baseline 3 applies.

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?

States a specific verb and resource ('Cancel a booking') plus the acting scope ('as the calendar owner'), so the core action is unambiguous. However, it never distinguishes itself from the sibling 'delete_booking', which an agent must disambiguate before choosing between them.

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 instruction 'Confirm with the user first' gives one actionable usage rule and 'as the calendar owner' implies a permission precondition. But there is no explicit when-to-use-this-vs-alternatives guidance, notably against delete_booking or reschedule_booking.

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