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

Annotations already declare readOnly, idempotent, and openWorld, so the safety profile is covered. The description adds genuinely new behavioral context: results carry masked RoomLast price bands and comparisons, exact private prices and booking must happen on RoomLast — a useful expectation-setting limitation.

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?

Four front-loaded sentences with no filler; the identity scoping, date representation, and return contents come in that order. The enumeration of return fields ('photos, breakfast, refundability...') is slightly long but each item conveys real capability.

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?

An output schema exists so return values need no prose explanation, and the description covers hotel identification, date handling, occupancy, and the masked-price limitation. The only missing piece is the prerequisite that a propertyId typically comes from search_accommodations.

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 85%, so the schema does most of the work, but the description still adds the date-mode semantics (dateIntent 'tonight' vs. the paired checkinDate/checkoutDate) and flags single- versus multi-room occupancy support, which maps to rooms and roomArrangements.

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?

States a specific verb and resource: 'Returns one named or identified hotel's live room offers.' The 'one hotel' scoping implicitly separates it from search_accommodations, but it never names the sibling, so the differentiation is inferential rather than explicit.

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 phrasing 'one named or identified hotel's' signals that a propertyId or hotelName must already be known, and it offers two date modes (tonight vs. explicit dates). However, it never says to run search_accommodations first to obtain a propertyId, nor does it exclude any situation or name a sibling tool.

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