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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, but the description adds substantive behavior beyond that. It distinguishes booked nights from nights that are not yet open, explains bookableFrom and bookableUntil, applies maxNights, and clarifies inclusive/exclusive range semantics.

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?

The description front-loads what the tool returns and then defines the ambiguous terms that affect interpretation. Every sentence earns its place by adding either semantics or usage constraints, with no redundant restatement of the name or title.

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?

There is no output schema, so the description carries the burden of explaining returned concepts, and it does so well. With read-only annotations and complete schema coverage, it gives enough context for an agent to invoke the tool correctly and interpret the results.

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, and the schema already documents each parameter. The description adds useful range constraints, such as defaulting to the next 90 days and allowing at most 365 days per call, though it does not add further detail about propertyId.

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 resource and output: booked nights and open date ranges with minimum-stay rules, and it explains the key returned fields. It does not explicitly distinguish this from siblings such as get_quote, but the availability-focused purpose is clear.

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 gives useful usage constraints, including a default range of the next 90 days and a maximum of 365 days per call. However, it does not say when to use this tool rather than get_quote or other siblings, so alternatives are only implied.

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