Prepare Booking

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

The description adds that the tool creates a draft and returns a browser handoff URL, going beyond annotations which only mark it as non-read-only and non-destructive. However, it does not detail the draft's lifespan or next steps.

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 with no redundancy; front-loads the core purpose and behavioral nuance.

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 6 parameters and no output schema, the description is too sparse. It lacks info on draft expiration, URL format, or error cases, which are important for correct invocation.

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 0% and the description does not explain any parameters, leaving the agent to infer their meaning from names alone. The description should at least summarize key parameters.

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 checks availability and creates a short-lived booking draft, distinguishing it from confirmation tools like confirm_booking.

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?

It explains that by default it returns a handoff URL rather than writing upstream, but does not explicitly contrast with search_hut_availability or clarify when to use this versus other booking-related tools.

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