booking_filter_results

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

No annotations are provided, so the description carries the behavioral disclosure burden. It clarifies the tool is client-side filtering (operating on in-memory results), which is non-destructive. It does not mention edge cases like empty results, but the behavior is straightforward for a filter.

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 sentences, no wasted words. The first sentence lists all filter options, and the second provides important guidance on alternative tool usage. Information is front-loaded and easy to parse.

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?

Given the tool has 7 parameters with 100% schema coverage and no output schema, the description is largely complete. It explains the client-side nature and return type ('filtered subset'). It could mention that results are limited to the most recent search, but that is already stated.

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 baseline 3. The description adds meaning by grouping filter types (price, review score, star rating, etc.) and clarifying the keyword filter applies to name/location. This adds context beyond the schema's brief descriptions.

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 clearly states it is a client-side filter over recent booking_search results, listing specific filter criteria (price, review score, star rating, free cancellation, breakfast, keyword). It distinguishes from sibling tools by noting that facility filtering is done server-side via booking_search.

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?

Explicitly states when to use this tool (client-side filtering after search) and when not (for amenities, use booking_search with the amenities argument). Provides a clear alternative, helping the agent decide correctly.

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