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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, and idempotentHint=false, covering the safety profile. The description adds useful behavioral context beyond annotations: it explains the return content (minimum rate, basic price/currency/availability) and emphasizes lightweight, fast responses.

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 description is front-loaded with an Overview, but it is bloated with redundant marketing phrases across multiple sections (e.g., 'Perfect for displaying price comparisons', 'Lightweight', 'Fast response', 'Ideal when displaying multiple hotels'). Each sentence does not earn its place, though the heading structure itself is clear.

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, the description usefully outlines the return shape (minimum rate, price, currency, availability) and overall purpose. Combined with rich annotations and 86% schema coverage, it is nearly complete for a read-only price lookup, though it omits minor operational details like timeout behavior or batch limits.

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 86%, so the schema itself documents nearly all parameters. The description only briefly mentions 'hotel IDs, dates, and guest occupancy' in Quick Start, adding little semantic detail beyond the structured fields.

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 states a specific verb+resource: 'Get the cheapest available rate for each hotel in your list.' It distinguishes from the fuller sibling endpoint by contrasting 'without loading full rate details' and 'main rates endpoint'.

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?

A dedicated 'When to Use' section gives clear scenarios (price ranges, comparisons, performance optimization, price filters) and an implicit exclusion when full rate options are needed. However, it does not name the alternative tool (e.g., post_hotels_rates) explicitly.

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