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

The readOnlyHint annotation already declares this is a safe read, so the bar is lower; the description adds real context by disclosing the response contents (total price, units available) despite there being no output schema, and by establishing the pre-booking sequencing. It does not mention pagination behaviour, though the page parameter's own schema text covers that.

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 short sentences front-load the purpose and return shape, then the usage rule, with the endpoint reference appended as a compact traceability note. No sentence is wasted and nothing important is buried.

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 10-parameter tool with no output schema, the description covers the core quote path but omits how the filter parameters affect scope and does not mention that results may be paged. Those gaps are recoverable from the schema text, leaving it adequate but not complete.

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 80%, so the schema already documents most parameters; the description only adds the high-level meaning 'given dates and guests', which maps to arrival/departure/numAdults. It says nothing about the scoping parameters (roomIds, offerIds, propertyIds) that let an agent narrow a quote.

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?

States a specific verb and resource ('Quote a stay') and enumerates what is returned — bookable offers with total price and units available — which is more informative than a generic 'get offers'. It stops short of explicitly naming how it differs from the close sibling beds24_get_room_availability, so it is clear but not fully differentiated.

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?

'Use before creating a booking' gives a concrete workflow context and implicitly points at the downstream sibling beds24_create_booking. There is no explicit when-not or alternative condition (e.g. when to prefer get_room_availability or list_fixed_prices instead), so it is clear context without exclusions.

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