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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses meaningful behavior: the 30-night cap, that prices are the TOTAL for the stay and exclude breakfast, and that each available room carries a book_url to the official engine. It does not mention rate limits or behavior when no rooms are available.

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 dense sentences, front-loaded with the core purpose and scoping constraint, followed by pricing and return-value information. No filler, though the parenthetical currency and duration notes are slightly compressed.

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 explains the return payload (room_id, book_url, total price per available room). It leaves the occupancy parameters' semantics and no-availability behavior unexplained, a modest gap for a 4-parameter read 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 50%: checkin/checkout are documented in the schema, while adults and children have no descriptions anywhere. The description contributes only the 30-night range constraint on the date parameters and adds nothing about occupancy limits (max 3 adults, 1 child), so the other half of the parameters remains undocumented.

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 states a specific verb+resource combination: availability and prices per room type for a stay, with currency (IDR) and duration limit. It is clearly distinguishable from book_room and list_room_types by implication, 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?

Usage context is implied by the max 30-night constraint ('séjour max 30 nuits') and by the pricing note, but there is no explicit guidance on when to call this versus list_room_types or before book_room. The agent must infer that this is the pre-booking availability check.

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