Hotel finalist details

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

Beyond the annotations (readOnlyHint/idempotent/openWorld), the description discloses a lot the structured fields do not: lock acquisition on the expensive path, the mismatch conditions (occupancy_mismatch, dates_mismatch, property_mismatch), echo-unknown and partial-quote semantics, and that reads do not evict stored searches while unknown/evicted ids return nothing. This is unusually rich behavioral context.

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?

The purpose is front-loaded, but the body collapses into long run-on sentences ('That quote is not the original stay when the city matches more than one place, the returned coordinates do not match...'), which makes the mismatch rules harder to parse than necessary. Information-dense but structurally weak.

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 not be explained, and the annotations plus description cover the safety profile and edge cases well. The remaining gap is the provenance/format of selection_id, which matters because it is the only required parameter.

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 description coverage is 0%, so the description carries the load, and it does explain room_rates thoroughly (default false, cost/lock implications of true). However selection_id is only hinted at via 'this process returned' and is never defined as the id from a prior search result, leaving one of two parameters underspecified.

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 and resource ('Read a hotel offer this process returned') and scopes it to offers already produced by the search flow, which implicitly separates it from the search_* siblings. It is clear, but it never names a sibling (e.g. recheck_offer, search_hotel_rooms) to reinforce the boundary, so it stops short of a 5.

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?

It gives explicit operating conditions for the room_rates flag: false returns the stored quote, does not search, and may run during another search; true requests a separate USD quote and takes the one-search lock. That is clear when-to-use guidance, though it never states when NOT to call this at all versus using a sibling tool.

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