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

Annotations only cover the read-only/idempotent safety profile; the description adds substantial context beyond them: the two sourcing modes (Staylist catalogue vs live provider), what data is returned, and the critical caveat that sample_estimate is a previously observed price, not a quote. It also discloses a privacy rule ('Never send names, email addresses or payment details').

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 purpose is front-loaded and the sentences are dense with useful detail rather than filler. The description is long and somewhat run-on in the return-value sentence, but nearly every clause earns its place.

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 enumerates what results contain (score, guest rating, amenities, photos, sample_estimate) and states operational constraints and a privacy rule. It is nearly complete for an 11-parameter search tool, with only a few filter parameters left unaddressed.

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 only 18%, so the description must compensate, and it does explain query semantics, the paired-date rule, and occupancy limits. However, it leaves several parameters (stars, min_rating, max_price_per_night, country_code, limit) undefined, so meaningful gaps remain.

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?

Starts with a specific verb+resource ('Find hotels') and immediately scopes it by city, name or preference queries, including that query words also match amenities and guest mentions. It clearly separates itself from siblings by routing booking-link needs to get_booking_link.

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?

Gives concrete usage constraints ('Supply both dates or neither', 'One room, 1–8 adults and up to 6 children') and names the alternative tool for booking links. It does not explicitly state when to prefer get_hotel or list_destinations, so it falls short of full when/when-not guidance.

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