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

With no annotations, the description carries the behavioral disclosure burden. It reveals that results are live, include all-in prices, are sorted cheapest first, and carry a bookingUrl that should always be shared. It does not cover edge cases like no availability, but the core runtime behavior is clearly disclosed.

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?

Every sentence earns its place: scope, usage timing, example queries, narrowing options, result behavior, and the sibling alternative. The core purpose is front-loaded and the description remains readable despite covering several useful details.

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 10 parameters, no output schema, and no annotations, the description still explains when to use the tool, how to narrow the search, what the results look like, and how to follow through with the bookingUrl. Required parameters are left to the schema, which fully documents them, so nothing essential is missing.

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 baseline is 3. The description adds light semantic color by showing example values for region and accommodation and clarifying maxPrice as a filter, but most parameter meaning is already fully documented in 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 uses a specific verb and resource: 'Find where Floreal Holidays has a stay available' across every location. It clearly distinguishes this tool from get_stay_price by noting the all-locations scope and explicitly naming the sibling for known single locations.

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 explicitly states when to use: 'whenever the guest has not picked a location yet', and provides concrete example queries. It also tells the agent when not to use it: 'For one known location get_stay_price is faster.' This is strong routing guidance.

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