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

Annotations only declare destructiveHint=true, but the description adds substantive behavior: the booking is not deleted (still visible via includeCanceled), seats are freed, the account's cancellation policy is bypassed, and therefore no cancellation fee is charged. These side effects are exactly what an agent needs before invoking a destructive operation.

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, front-loaded with the action and its consequences, with no filler. Every sentence conveys information an agent would otherwise lack.

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 the critical unknowns for a destructive tool: soft-delete semantics, seat release, fee exemption. It does not say whether the cancellation can be reversed/restored or what the API returns, though no output schema exists to offset that gap.

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%, so all six parameters (reason, notifyCustomer, notifyUsers, cancelRemainingSeries, trackInCustomerHistory, bookingNumber) are already documented in the schema. The description adds no parameter-level detail beyond what the structured fields provide, so the baseline of 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 precise verb+resource ('Cancel a booking') and is unambiguously distinct from siblings like bookeo_create_booking and bookeo_update_booking. The closing line even names the underlying API operation (DELETE /bookings/{bookingNumber}), removing any doubt about intent.

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 explains the effect of canceling (frees seats, stays in the system, no fee), which indirectly signals when it is appropriate, but it never states when to use this versus bookeo_update_booking or bookeo_create_hold, nor any prerequisites. Usage is implied rather than guided.

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