Availability & prices

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

With no annotations, the description carries disclosure burden. It adds 'live' data context and the dates format, but doesn't disclose response structure, error behavior, or whether both checkout and nights causes issues. It's acceptable but not rich.

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 with a clear lead, date format, and usage rule. 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?

Given the complexity (8 params, no output schema, no annotations), the description communicates the core purpose and essential parameter constraints. However, it omits expected return values (e.g., room types, price breakdown) and edge-case behaviors, leaving the agent with gaps for a complete interaction.

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 covers only 25% of parameters. The description adds two important semantic details: date format (YYYY-MM-DD) and the checkout-vs-nights mutual exclusivity. This goes beyond schema, though other params like adults/children/rooms are left to names and schema types.

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 identifies the tool as 'Live availability and prices for a specific stay', specifying the resource (availability/prices) and scope (specific stay). It also positions it as the primary tool for 'is there a room and how much' questions, distinguishing it from siblings like get_rates or get_best_rate.

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 states this is the primary tool for room availability/pricing queries, providing clear usage context. It also gives a key usage rule ('Provide checkout OR nights') but does not explicitly mention when to prefer alternatives like get_rates for pure pricing or get_calendar for date-level views.

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