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

Annotations already declare this as read-only, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds useful behavioral scope: results are constrained to the same city and ranked by closeness across comfort filters, which is not captured by annotations or schema.

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?

Two tight sentences with no filler. The core selection rule is front-loaded, and the cheaper_only hint follows immediately as a natural variant.

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?

For a read-only similarity finder with one required parameter and no output schema, the description sufficiently explains what is returned (hotels in the same city with similar comfort profiles) and the main filtering variant. It could mention limit defaults or date behavior, but the schema already covers those.

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 100%, so all seven parameters are already documented, including cheaper_only, max_price, and dates. The description reinforces the meaning of cheaper_only and the comfort-profile comparison, but adds little parameter-level detail beyond the schema.

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 resource (hotels) and a precise selection rule: same city with the comfort profile closest to a given hotel, plus the cheaper_only variant. It is easy to distinguish from compare_hotels or search_hotels, though it does not name those siblings 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?

The phrase "Use cheaper_only for 'like this one but cheaper'" gives one concrete usage scenario, but there is no guidance on when to choose this tool over search_hotels or compare_hotels, nor any exclusions or prerequisites.

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