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

readOnlyHint=true already tells the agent this is a non-mutating read, so the description's main addition is that the result carries prices and unit counts. It does not disclose pagination behavior even though the schema's page parameter references pages.nextPageExists, nor any auth/rate-limit context. Useful but shallow beyond the annotation.

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 with the core value (bookable offers with price and units) front-loaded, plus a short API path. Tight overall, though the bare endpoint reference adds little for an agent that already has the tool name.

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 read tool with no output schema, the description covers the required-parameter intent (dates, guests) and the return shape at a high level, which is the minimum an agent needs. It leaves pagination handling and the undocumented agentCode/numChildren parameters unaddressed, so it is adequate rather than 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 description coverage is 80%, so the schema already documents arrival, departure, roomIds, offerIds, propertyIds, includeTexts and page. The description only gesture-references "given dates and guests" and adds no format, constraint, or filtering detail beyond the schema, so the baseline 3 applies.

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 (quote) and resource (room offers) and further specifies the payload: total price and units available per room for given dates and guests. This separates it reasonably from the bare availability sibling, though it never names beds24_get_room_availability directly, so the differentiation is inferential rather than explicit.

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 position, which is clear context for when to invoke it. It stops short of naming an alternative or an exclusion (e.g. when to prefer get_room_availability for a simple calendar check), so it lands at 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.