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

The description frames the tool purely as a read/query operation, while the annotations declare readOnlyHint=false and destructiveHint=true. That is a direct conflict about the tool's side effects, and the description adds no compensating behavioral context (caching via no_cache, pagination via next_page_token, or result-shape info) that would clarify the real 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?

A single front-loaded trigger sentence with no filler; the enumeration of facets is scannable. It is slightly redundant in re-listing concepts (dates, ratings, amenities) that the schema documents exhaustively, but nothing is wasted.

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 27-parameter search tool with no output schema, an agent can still call it correctly thanks to full schema documentation, but the description says nothing about pagination flow, caching semantics, or vacation-rental-vs-hotel mode switching. Adequate, not complete.

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 100% across all 27 parameters, so the schema already explains q, dates, amenities, filters, no_cache, next_page_token, etc. in detail. The description contributes no parameter-level meaning beyond the general list of queryable facets, so the baseline 3 applies.

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 a specific resource (Google Hotels) and enumerates what the tool surfaces — search results, prices, check-in/check-out dates, ratings, amenities, property types and filters — so an agent knows this is the hotel-search scraper. It never contrasts itself with the neighboring lodging tools (booking_hotellist, airbnb_product), so differentiation must be inferred from the name alone.

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 supplies a trigger condition ('when the user needs to query...'), which is the minimum viable routing guidance. There is no when-not guidance, no mention of prerequisites (check-in/check-out dates are required), and no pointer to sibling lodging tools that might be preferred.

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