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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered; the description goes further by disclosing the response payload (name, location, starting rate, amenities, cancellation terms, booking link) and the behavioral difference between a bare search and one with dates/guests. It omits pricing-currency behavior and result limits, which keeps it below a 5.

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?

Three sentences, zero filler, front-loaded with the differentiator (direct booking, no OTA commission) before the return list and usage trigger. Every sentence carries information an agent needs.

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 correctly compensates by enumerating the returned fields, and it covers when to call and what the optional params change. A 7-param tool with only one required param could have clarified how query and city interact, which is the remaining gap.

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 a middling 57%, and the description only adds meaning for the date/guest parameters by tying them to live availability. It says nothing about the query-vs-city relationship, country, or the max_price currency ceiling, leaving the undocumented half of the schema unclarified. Baseline 3 is appropriate.

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 and resource ('Search hotels') plus a distinguishing qualifier: bookable directly with no OTA commission via Pickrate. It also enumerates the returned fields, so an agent can tell it apart from get_hotel (detail lookup) and check_agent_readiness without opening any schema.

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?

Gives an explicit trigger ('when a traveller asks for a hotel in a city or area') and explains the conditional behavior of optional params (dates/guests unlock a live-availability booking link). It stops short of naming get_hotel as the follow-up alternative for deep-detail lookups, so routing between siblings is only half covered.

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