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

readOnlyHint already declares the safety profile, but the description adds real value: it confirms nothing is booked, states the required auth scope 'read:availability', and describes the shape of the pricing breakdown (fees, taxes, deposit, total). It does not cover behavior when no availability exists, but the added context is substantial.

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?

Two tight sentences, with the payload scope front-loaded and the mutation warning and auth requirement trailing. 'Books nothing' mildly restates readOnlyHint, a small redundancy, but nothing else is wasted.

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?

With no output schema, the description usefully enumerates the returned fields, and it flags the required scope, which is critical for a scoped API. Minor gaps: no note on how unavailable dates are represented and no occupancy constraint hints, but an agent can call it correctly.

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 coverage is 86%, so dates, adult/child defaults and coupon semantics are already documented in the schema. The description adds no parameter-level meaning beyond that, and the one undocumented parameter (number_of_pets) is left unexplained in both places. Baseline 3 applies.

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 concrete verb ('Search what the property can sell') tied to a specific resource for a stay, and enumerates the returned payload (rate types, fees, taxes, deposit, total). This differentiates it from rate-type and inventory siblings implicitly via 'price for the whole stay', though no sibling is named explicitly.

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?

'For a stay' and 'price for the whole stay' imply the whole-stay quoting use case versus nightly rate lookups, but the description never states when to prefer this over thinkreservations_get_daily_rates or get_inventory. No exclusions or prerequisites beyond the scope requirement are given.

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