hemmabo_booking_cancel

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

Annotations mark destructive and idempotent; description reinforces these with specific behavior (cancelling already-cancelled returns same status). Also adds authorization requirements and rate-limiting, going beyond 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?

Five sentences, each efficiently adds value: purpose, usage guidance, exclusion, authorization, behavior. No redundancy.

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?

Given simplicity of tool and coverage by annotations, description fully covers purpose, usage, authorization, and behavior. No missing information for effective use.

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 coverage is 100%, but description adds meaningful context: reservationId source (from checkout/create) and reason purpose (for the host). Provides useful direction beyond schema definitions.

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 confirmed booking and processes a Stripe refund. It distinguishes from sibling tools like reschedule or status by specifying the exact action.

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 expire automatically). Could mention alternatives like reschedule by name for full clarity.

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