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

Adds substantial context beyond the readOnly/openWorld annotations: calendars are live but refreshed only about every 2 hours, so results can lag reality. It also discloses the end-exclusive range convention, that a checkout day is bookable as a check-in, the minimum-stay filter on openWindows, and the clippedAtWindowEnd flag meaning a gap may extend past 'to'.

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?

Front-loaded with what is returned and how fresh it is, and every clause carries operational meaning. It is dense and the three-home list duplicates the enum descriptions, which is the only real redundancy.

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?

With no output schema, the description carries the burden of describing returns, and it largely does: booked ranges, openWindows, and the clippedAtWindowEnd flag. It stops short of a full response shape (e.g., whether each booking includes guest counts or just dates), which is the remaining gap.

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 the baseline is 3, but the description genuinely adds: the 400-day maximum window and the default today-plus-180 are not in the schema, and the end-exclusive meaning of 'to' is spelled out in plain language. Property semantics (sleeps, minimum stay) are repeated from the enum description rather than newly added.

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+resource: returns booked date ranges and open windows for three named homes from live calendars. This is clearly distinct from the siblings get_quote and request_booking, which do quoting and booking rather than lookup, so an agent can select it without opening the schema.

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?

Usage is implied rather than stated: an agent can infer this is the lookup to run before get_quote or request_booking, but the description never names those siblings or says when not to call it. The explicit defaults (today plus 180 days, 400-day cap) give useful framing but not routing guidance.

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