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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the bar is lower, and the description adds substantial non-obvious context: tax-inclusive vs tax-exclusive scope per seller, the Agoda dual-entry (method=screen vs Lite API), and the caveat to compare only tax-inclusive scopes. It stops short of noting freshness, caching, or failure modes.

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?

The English explanation is front-loaded and dense with genuinely useful detail, but the entire content is then repeated verbatim in Korean, roughly doubling length with no added information for an agent reading either language. The core is efficient; the duplication is not.

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 and a fairly complex result shape (hotels × sellers × two day-types), the description does well to explain the seller list, the reason Agoda returns two entries, and the price_scope field. A fuller sketch of the returned record structure would close the remaining gap.

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% and both parameters (city, limit) are fully documented in the schema, including accepted Korean/English names and airport codes. The description adds no syntax beyond that, so the baseline of 3 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?

The description names a specific verb+resource (get hotel prices) and precisely scopes the result: the 20 most-reviewed hotels for a popular city, priced for 2 adults on the next weekday and weekend. It is trivially distinguishable from siblings like get_direct_flights, get_tours, and get_demand_index.

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 a popular city' implies the applicable context, but there is no explicit when-to-use/when-not guidance and no alternative named. Because the sibling tools address entirely different resources, the risk of mis-selection is low, leaving this merely implied.

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