book_hotel

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

Annotations indicate idempotentHint=true and openWorldHint=true. The description adds valuable behavioral context: returns a checkout URL, guest pays directly, hotel confirmation number, loyalty points apply, and a 1Stay booking fee. It also warns against collecting payment info, which is crucial for safe agent behavior.

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 thorough and informative, with key information front-loaded. Every sentence adds value, though it could be slightly more concise. Still effectively structured for an AI agent.

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 absence of an output schema, the description adequately explains the return value (checkout URL), prerequisites, constraints, and what not to do. It covers all necessary context for a booking tool with multiple dependencies.

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 has 100% coverage with clear descriptions for all 8 parameters. The description adds extra meaning by emphasizing that rate_code must come from get_hotel_details and expires in ~15 min, and that external_reference_id supports idempotency, aligning with the idempotentHint annotation.

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 books a hotel room and returns a secure checkout URL. It distinguishes itself from siblings like cancel_booking, get_booking, and search_hotels by focusing on the booking action and referencing the prerequisite get_hotel_details for rate_code.

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 states when to use (after obtaining a valid rate_code via get_hotel_details) and when not to use (never collect payment info, never suggest calling hotel or booking elsewhere). It also provides guidance for expired rate codes, directing to call get_hotel_details again.

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