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

With no annotations provided, the description carries the full burden. It discloses the atomic hold for 30 minutes, the return of a Stripe Checkout URL, and that confirmation occurs only after payment. It also notes that no account or API key is needed.

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?

The description is two sentences, efficiently conveying purpose, behavior, and usage. Every sentence adds value with 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 the tool's complexity (booking with payment integration), the description covers key aspects: hold duration, checkout URL, payment requirement, and autonomy. No output schema exists, but the description explains the return value. The omission of cancellation or failure handling is acceptable.

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?

The description does not add significant meaning beyond the input schema. Schema covers 4 of 6 parameters with descriptions; the description refrains from elaborating further. The overall process is clear, but parameter-level guidance is minimal.

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's purpose: to book Wanaka Haus by atomically holding dates and returning a Stripe Checkout URL. It distinguishes itself from sibling tools like search_availability and cancel_booking by focusing on the booking 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?

The description explains when to use the tool (to create a booking) and provides guidance on the next steps (give URL to user for payment or use agent wallet). It does not explicitly state when not to use it, but the context is clear enough.

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