get_hotel_details

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds valuable context: payment flows (guest pays hotel, 1Stay fee added), loyalty points eligibility, and room type clarifications (run-of-house, suite definition). No contradiction with 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?

Description is brief, front-loaded with main purpose, and uses separate paragraphs for payment and room notes. Each sentence adds value, though the room type explanations could be slightly trimmed. No wasted words.

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 lacking an output schema, the description lists all return elements (room types, rates, amenities, policies, rate_codes) and adds payment and eligibility context. For a simple 5-parameter tool, 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% with each parameter descriptively named. The description adds no extra meaning beyond the schema for parameters; it only reiterates date format and defaults, which the schema already includes. Baseline 3 is appropriate.

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 retrieves rates and room details for a specific hotel, enumerating return fields (room types, live rates, amenities, cancellation policies, rate_codes) and explicitly linking rate_codes to the sibling tool book_hotel, which distinguishes it from search_hotels and booking tools.

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 implies when to use (before booking, to get rate_codes) but does not explicitly state when not to use or compare with alternatives like search_hotels for listing hotels. The sibling list exists but no direct guidance in description.

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