hotels_reviews_archive

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It clearly states it returns public guest reviews only, paginates one page per call, and excludes Booking, account, and private review data, which gives agents an accurate insight into the tool's behavior.

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 description is four sentences long and every clause serves a purpose: resource, return content, pagination mechanics, property_id source, and exclusions. It is slightly repetitive around something but not wasteful enough to lose more.

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?

Given no output schema and no annotations, the description provides enough context to call the tool correctly: it states what is returned, how to paginate, how to obtain property_id, and what is not included. It is not fully complete because request structure and rate limits are unspecified, but it is adequate for an agent to use the 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?

The schema's request object is a high-level placeholder, but the description adds real parameter semantics by explaining that page and page_size control pagination and that property_id matches a search result's numeric property id. This meaning extends beyond what the input schema alone provides.

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 names the exact resource ('Hotels.com guest reviews'), the action ('List'), and the main fields returned, so the purpose is clear. It does not explicitly differentiate itself from the sibling 'hotels_reviews' tool other than through the 'archive' wording, so it stops short of a full 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?

The description gives concrete operational guidance: use page and page_size to paginate, and source property_id from a Search response's properties[].id. It does not mention when to choose this tool over hotels_reviews or other review tools, though the usage instructions themselves are clear.

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