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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description still adds real context beyond them: results are limited to direct-stay reviews (not third-party channels) and ordered newest first, which affects how an agent should present results.

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 most decision-relevant facts front-loaded: what is returned, from where, in what order. Nothing wasted.

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 and annotations cover the safety profile, so the description needn't explain return values. It supplies the two non-obvious facts (source scope, sort order) but says nothing about defaults or whether the summary is computed over all reviews or only the returned page.

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 100%, with limit and minRating both documented in the schema, so baseline 3 applies. The description adds no filtering or default-behavior detail beyond that, and never mentions the minRating capability at all.

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?

Names the resource precisely: a rating summary plus verbatim guest reviews, scoped to direct stays, sorted newest first. This clearly distinguishes it from siblings like get_property_overview or get_policies, though there is no explicit sibling callout.

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 implied by the content (an agent wanting guest sentiment would pick this), but the description never states when to use it instead of get_property_overview or compare_to_alternatives, nor any exclusions. The 'direct stays' scope is the only routing signal.

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