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

No annotations are provided, so the description carries the full burden. It adds useful behavioral context ('room-level') and lists output content (availability, pricing, amenities). However, it doesn't disclose potential side effects, rate limits, or that it's read-only, which would be expected given no safety 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?

The entire description is a single, front-loaded sentence that quickly conveys the tool's purpose without any fluff. It avoids unnecessary repetition and is perfectly sized for quick scanning.

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?

Even though there is no output schema, the description covers the key output categories (availability, pricing, amenities) and the input parameters are thoroughly documented. The description is sufficient for a well-understood 'details' operation, though it could have included return format nuances if needed.

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?

All 7 parameters have rich descriptions that go beyond schema basics. For example, the 'live' parameter explains the trade-off between accuracy and speed, and 'hotelId' clarifies its source. These descriptions significantly enhance the agent's ability to set parameters correctly (e.g., including booking links, date format, and constraints).

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 uses a specific verb ('Fetch') and resource ('room-level availability, pricing, and amenities for a specific hotel') and clearly distinguishes from search siblings by emphasizing 'specific hotel' and 'stay dates'. It immediately communicates the tool's scope and differentiates it from the related skiplagged_sk_hotels_search.

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 provides clear context on when to use the tool (for a specific hotel and stay dates), implying it's for retrieving details rather than searching. However, it doesn't explicitly mention alternatives or exclusions, though the parameter description for 'hotelId' adds 'from search results' to guide sequencing.

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