get_hotel_details

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

No annotations are provided, so the description must disclose behavior. It states the tool returns details but does not mention side effects, read-only nature, rate limits, or error handling. Minimal behavioral context beyond parameter formats.

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 purpose sentence followed by a focused parameter list. No redundant information, well-structured and front-loaded.

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?

Combined with output schema (present), the description covers the essential behavior. It lists what the tool returns and explains all parameters. Lacks information on error conditions or pagination but sufficient for a detail endpoint.

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 input schema has 0% description coverage, but the description provides clear, actionable semantics for all 5 parameters: hotel_id source, date format, defaults for adults and currency_code, and examples. Fully compensates for missing schema descriptions.

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 detailed information about a specific hotel, listing included data types (reviews, facilities, policies, booking links). It differentiates from sibling tools like 'get_hotels' (listing) and 'get_attraction_details' (attractions).

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 the tool should be used after obtaining a hotel_id from 'get_hotels' results, but does not explicitly state when to use or avoid it, nor contrasts with similar tools like 'get_attraction_details'.

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