hemmabo_booking_cancel

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

Discloses key behaviors: Stripe refund processing, refund calculation based on cancellation policy, and return of confirmation with refund amount and status. Lacks explicit mention that cancellation is irreversible, but overall strong for a tool with no annotations.

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 sentences, each earning its place: purpose, usage guidelines, and return values. Front-loaded with main action, 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?

With no output schema, description provides return values (confirmation, refund amount, status) and prerequisites (confirmed booking only). Covers essential details for a cancellation tool.

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?

Adds context beyond schema: reservationId is a UUID from specific sources (booking_checkout or booking_create), and reason is optional but recommended for host notification. Schema coverage is 100%, and description enhances meaning.

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 cancels a confirmed booking and processes a Stripe refund, with specific verb and resource. It distinguishes itself from sibling tools like hemmabo_booking_create and hemmabo_booking_checkout.

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 says when to use (guest requests cancellation) and when not to use (pending/unpaid bookings, which expire automatically), providing clear usage boundaries.

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