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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: the response is static/public metadata and explicitly excludes date-specific prices and availability, which prevents the agent from misusing it for pricing. It does not mention auth or rate limits, so it falls short of 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?

Two sentences, zero waste. The primary purpose and inclusion scope are front-loaded, with routing/exclusions trailing. Every clause 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?

An output schema exists, so return values need not be described; the description still usefully scopes what is and isn't returned. Combined with annotations covering read-only/open-world status and full param docs, an agent has everything needed to call this correctly.

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% and the single url parameter is fully documented in the schema with an example and a pointer to hotels_search. The description adds no further parameter detail, so the baseline of 3 for schema-covered params 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?

States a specific verb (fetch) and resource (static public Hotels.com property metadata) and enumerates the payload (address, rating, images, amenities). It immediately distinguishes itself from sibling tools by naming hotels_rates, hotels_offers, hotels_reviews, and hotels_search.

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 explicit routing rules: use hotels_rates or hotels_offers for pricing, hotels_reviews for reviews, hotels_search to discover properties. It also states an exclusion (date-specific prices and availability) so the agent knows when NOT to use it. Nothing is left to inference.

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