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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description usefully adds that pricing is 'live' (real-time fetch) and that the comparison batch is capped at 2-5 hotels, but it says nothing about partial failures, unknown hotel ids, or rate/availability limits.

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 sentence: verb and scope first, then the compared dimensions. The attribute list is long but each item is a distinct output field the caller is deciding on, so every token earns its place.

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 does a fair job of previewing the return (price, stars, rating, amenities, cancellation, breakfast, check-in/out, differences). However, for a 6-parameter tool with zero schema descriptions, the guest-composition and currency inputs remain unexplained, leaving a gap an agent could stumble on.

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% across 6 parameters, so the description carries the burden and only partially meets it: it implies hotel_ids ('2 to 5 hotels') and the date inputs ('for given dates') but never mentions adults, children, or currency, which are the parameters most likely to be mis-set. The occupancy and currency defaults are left entirely to the schema titles.

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 (compare) and resource (hotels) plus an explicit scope ('2 to 5 hotels side by side for given dates'), which naturally separates it from sibling single-item tools like get_hotel_details and from discovery tools like search_hotels. It also enumerates exactly which attributes are compared, so an agent knows what it gets back.

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 '2 to 5 hotels' constraint and 'for given dates' imply the intended context (side-by-side evaluation of already-known hotels), but no alternative is named and no when-not condition is given. An agent must infer that this is the follow-up to search_hotels rather than a replacement for it.

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