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

Beyond the readOnly/idempotent/openWorld annotations, the description discloses the rate limit, the pricing assumption (2 adults, 1 room, USD, lowest total), and critically that the tool does not transact — the traveler picks a room and pays on the linked seatac.co page via rooms_url. That booking-handoff boundary is the single most important behavioral fact for an agent to know.

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 dense sentences, front-loaded with the resource and pricing basis before the booking handoff and rate-limit caveat; nothing is filler. The nested parenthetical '(2 adults, 1 room, USD, our price as seatac.co shows it)' is slightly crammed and could read more cleanly without losing content.

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 an output schema present, return values need no prose, and the description still covers pricing basis, the rooms_url follow-on action, and the rate-limit constraint. Remaining ambiguity — sold-out inventories, tax/fee inclusion beyond 'total', or behavior for past dates — is modest for a read-only pricing tool.

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 100% with an enum on `near`, so the schema already carries the parameter definitions. The description restates 'near is a cruise pier (pier-66, pier-91) or a hotel area' — essentially the schema text — and adds no detail on date semantics or limit behavior. Baseline 3 applies since the schema does the heavy lifting.

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 opening sentence names the specific resource (live room prices for Seattle-area hotels), the date scope, and the exact basis of the number returned (lowest total for the stay, 2 adults, 1 room, USD). It also clarifies that the value reflects seatac.co's displayed price rather than a generic market rate, which separates it from broader siblings like recommend_hotels_with_rides.

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?

Usage is clearly scoped: supply a cruise pier or hotel area plus check-in/check-out dates, and 'reuse results instead of re-checking' gives an explicit caching directive driven by rate limits. What is missing is an explicit alternative — it never says to use recommend_hotels_with_rides for recommendation-style discovery instead of live pricing.

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