Get Hotel Details

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

Annotations already declare readOnlyHint and idempotentHint, so the description adds value by detailing the return structure (rooms, rate plans, prices, cancellation policies) and efficiency ('One RPC'). It does not contradict 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?

Three sentences, each serving a distinct purpose: purpose, return structure, and alternative. Front-loaded with the core action. No superfluous information.

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?

The description covers the output (rooms, plans, prices, policies), prerequisite (entity_key from search_hotels), and sibling tool. It mentions 'One RPC' for efficiency. Missing details like date format or error handling are partially mitigated by the presence of an output schema.

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?

Despite 0% schema description coverage, the description gives context for entity_key ('from search_hotels') but does not explain check_in, check_out, or currency beyond what the schema provides (type, defaults, required status). The parameter names are self-explanatory, but the description could add more.

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 provides 'Deep detail for ONE hotel' and requires entity_key from search_hotels, effectively differentiating it from siblings by specifying single-hotel focus versus multi-hotel comparison.

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 prerequisite ('Requires entity_key from search_hotels') and provides an alternative ('For multi-hotel deep comparison use search_hotels_with_details instead'), guiding the agent on when to use this tool versus alternatives.

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