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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and external-fetch behavior are covered. The description adds that the payload is 'static public metadata' (immutable, publicly available, not rate/availability data), which is useful context, but says nothing about pagination, freshness or what subset of the page is returned.

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 with no filler. It is appropriately terse, though the brevity comes at the cost of some detail an agent would find useful.

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 fields need not be described, and annotations cover the read-only/public nature. What is missing is usage routing against the five sibling hotels_* tools and any explanation of the url argument, leaving the definition minimally viable for a detail-lookup 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?

With only one parameter and 0% schema description coverage, the description must carry the burden of explaining 'url'. It implies the URL should point at a canonical Hotels.com property page, but gives no format guidance (full URL vs. path, canonicalization rules), and the optional/required status (0 required) is unexplained.

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 gives a specific verb (Get) and resource (static public metadata for a canonical Hotels.com property page), and the word 'static' implicitly separates it from dynamic siblings like hotels_rates, hotels_offers and hotels_reviews. It is clear, though it never names an alternative sibling explicitly.

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?

Usage is only implied: the mention of a 'canonical property page' suggests the tool is for detail lookups when you already have the page, and 'static public metadata' hints at non-rate, non-review content. There is no explicit when/when-not statement or pointer to hotels_search, hotels_rates or hotels_reviews.

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