get_hotel_details

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

With no annotations provided, the description carries the full burden. It states the tool 'Get detailed information', implying a read-only operation. However, it does not disclose any behavioral aspects such as side effects, rate limits, or authentication requirements. The description is adequate but lacks richness.

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 concise: a single paragraph followed by a list of arguments. Every sentence adds value, and the structure is front-loaded with the purpose. No redundant or 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?

Given the tool has an output schema, the description appropriately omits return value details. It mentions the types of information returned (reviews, facilities, etc.) which is sufficient. With 5 parameters and required fields noted, the description is largely complete, though it could improve by noting data freshness or error scenarios.

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 schema description coverage is 0%, meaning the description must compensate. It thoroughly explains each parameter: hotel_id as from get_hotels, checkin_date and checkout_date in YYYY-MM-DD format, adults defaulting to 2, and currency_code with examples (KRW, EUR, USD). This adds significant meaning beyond the schema.

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: 'Get detailed information about a specific hotel including reviews, facilities, policies, and booking links.' This specifies the verb (Get), resource (hotel details), and the scope (specific hotel, including various aspects). It distinguishes itself from sibling tool 'get_hotels' which presumably lists hotels.

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 hints at usage context by noting that 'hotel_id' comes 'from get_hotels results', implying this tool is used after obtaining a hotel ID. However, it does not explicitly state when not to use it or provide alternatives. This is clear context but lacks explicit exclusions, fitting a score of 4.

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