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

Annotations declare readOnlyHint=true and openWorldHint=true, telling the agent this is a safe, internet-facing read, so the description only needs to add context beyond that. It adds the useful fact that reviews are 'normalized' and that search_text performs a free-text search, but says nothing about pagination behavior, rate limits, or the effect of an empty search_text. Adequate but thin given the annotations already carry the safety profile.

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?

One well-formed sentence, front-loaded with the return value and the entity, and mentioning the key optional parameter. It earns its place with no filler, though it is arguably too terse for a 7-parameter tool.

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?

For a 7-parameter read tool with an output schema and readOnly/openWorld annotations, the description does the minimum: it identifies the resource and the optional filter. It omits usage routing, pagination semantics, and the fact that two parameters are required, leaving the agent to infer a lot from the schema alone.

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%, so the parameter baseline is already 3, and the description adds meaning by flagging that search_text is an optional free-text filter over review content, which clarifies its scope beyond the schema's one-liner. It does not explain page/limit interactions or the hotel_score/destination_id provenance, but the schema already documents those.

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 (Returns) and resource (normalized guest reviews), and names the platform (Booking.com) and the entity scope (a hotel), which distinguishes it from generic 'reviews' siblings. It does not name or differentiate against the very close siblings booking_attractions_reviews, hotels_reviews, or expedia_properties_reviews, leaving ambiguity about which review tool to pick for a Booking.com property.

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 description implies the usage context (you need a hotel_id) and hints that search_text is optional, but it never states when to use this tool versus booking_hotel_detail, hotels_reviews, or booking_attractions_reviews. There is no when-to-use or when-not-to-use guidance and no prerequisites (e.g. whether hotel_id must come from a prior search).

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