get_hotel_details

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

Beyond annotations (readOnlyHint=true, etc.), the description adds critical behavioral context: rate_code expiration, direct guest payment, the 1Stay Booking Fee, and room type clarifications. This fully informs the agent of important side effects and constraints.

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 moderately sized with clear front-loading of purpose. All sentences add unique value without repetition. Could be slightly more concise, but it's well-structured.

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?

Despite no output schema, the description explains what is returned (room types, rates, amenities, policies, rate_codes) and covers key behaviors (expiration, payment, fees, room types). Given the tool's complexity and annotations, this is comprehensive.

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%, so baseline is 3. The description adds little to individual parameter meaning beyond what the schema provides, but it does provide general context like rate_code expiry and room type notes that indirectly relate.

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 retrieves 'room types, live rates, amenities, cancellation policies, and rate_codes' for a specific hotel, using a specific verb and resource. It distinguishes itself as a prerequisite for booking, contrasting with sibling tools like 'book_hotel'.

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 'Required before booking' and mentions rate_codes expire in 15 minutes, guiding when to use. It also explains payment and fee structure. No exclusions or alternatives named, 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.