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

Beyond the read-only annotations, it discloses that results include live total USD prices for the whole stay, that required fees are included but the refundable security deposit is excluded, how default sorting works, and that unsupported parameters are rejected. These are meaningful behavioral details for an agent deciding whether and how to call it.

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 compact and front-loaded: purpose, return values, sort behavior, paging, validation behavior, and alternatives are each covered in a single efficient sentence. There is no filler.

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 complex 18-parameter search tool with no output schema, the description covers the search semantics, price return behavior, sorting, paging, and alternatives for related lookups. The schema carries the per-parameter detail, so an agent has enough context to call it correctly.

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%, so the schema already documents all 18 parameters thoroughly. The description adds only limited extra meaning, mainly default sort behavior and offset-based paging, both of which are also present in the schema, so the baseline of 3 is appropriate.

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 verb and resource (search vacation rentals), defines the location and availability criteria, and states what is returned. It also distinguishes the tool from get_quote and get_property_details, making its role clear even without opening the schema.

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?

It provides clear usage guidance: search by dates and party size, sort with best_fit or price_low, page with offset, and use get_quote or get_property_details for other needs. The main gap is that it never mentions the sibling check_availability, so one relevant alternative is left to inference.

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