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 that the data is 'public' and that results are 'summaries' rather than full rate detail, which is useful extra context, but it says nothing about coverage, freshness, or locale/currency 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 tight sentence with the resource and scoping constraint front-loaded and zero filler. It is efficient, though its brevity is partly a symptom of the coverage gaps rather than pure economy.

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, but for a six-parameter tool with 0% schema coverage the description should at least clarify the undocumented optional filters and how it differs from hotels_rates. As written it is under-specified for correct invocation.

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 six parameters, so the description must carry the burden. It only accounts for property_id, check_in and check_out via 'one property and date range', leaving adults, locale and currency completely unexplained in both schema and description.

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 (Get) plus resource (Hotels.com room offer summaries) and scopes it to one property and a date range, which is far more than a restatement of the name. It does not, however, distinguish itself from the very similar sibling hotels_rates, leaving the agent to guess which one returns offers versus rates.

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 phrase 'for one property and date range' implies the calling context, but there is no explicit when-to-use or when-not-to-use guidance and no mention of the obvious alternative, hotels_rates. An agent cannot tell from the description which of the two pricing tools to pick.

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