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

Annotations already establish readOnlyHint=true, idempotentHint=true, and non-destructive behavior. Beyond that, the description adds meaningful behavior: only properties actually available are returned when dates are provided, and the nightly rate should not be trusted as the stay total. This is useful context not captured by annotations.

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?

Three sentences, each earning its place: the first states what the tool searches, the second explains availability behavior with dates, and the third gives essential pricing guidance. It is front-loaded and free of 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?

With 11 parameters, no output schema, and no required fields, a complete description would ideally mention what fields appear in results or how ambiguous destinations are handled. However, the schema covers parameter semantics thoroughly, and the description adds the two most critical behavioral rules: date-based availability filtering and always using get_live_quote for the true total.

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 the schema already explains all 11 parameters in detail. The description adds only a high-level summary of search dimensions ('destination, dates, group size, bedrooms and amenities') and the date-dependent availability behavior, which slightly reinforces but does not materially extend the schema's parameter documentation.

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 and resource: 'Search Luxury Lodging's directly bookable vacation rentals.' It names the main search facets (destination, dates, group size, bedrooms, amenities), and this clearly distinguishes it from siblings like get_property_details and get_live_quote, which serve different purposes.

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 description gives clear context for using the tool: provide dates to get truly available propertiescars, and never use the nightly rate as the final price. It points to get_live_quote as the correct quoting alternative. However, it does not explicitly state when not to use this tool in favor of get_availability or list_markets.

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