Room calendar

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

Annotations already declare read-only, idempotent, non-destructive, so the safety profile is covered. The description adds genuinely non-obvious behavior: the pricing rule ('a night is priced on its arrival day') and the calendar horizon limit ('open only to the end of next Jalali month'), which an agent cannot infer from annotations or schema.

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 tight paragraphs: the first front-loads the returned fields, the second carries the pricing rule, horizon limit, and usage/handoff. Every sentence earns its place with no filler.

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?

An output schema exists, so return structure need not be re-explained. Combined with annotations and 100% schema coverage, the description supplies the remaining operational context (pricing rule, horizon, usage, next step) an agent needs to call this correctly.

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 a semantic constraint relevant to the start/end parameters — the calendar only opens to the end of next Jalali month — which goes beyond the field-level docs and explains truncation behavior.

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 ('Get a room's calendar day by day') and enumerates the exact per-day fields returned (discounted/undiscounted nightly price, availability, instant booking, min/max nights, weekend, holiday, late checkout). It also distinguishes itself from siblings by routing to ot_price_quote for stay pricing.

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?

Gives clear usage contexts ('find free dates, the cheapest nights or allowed stay lengths') and names the natural next tool (ot_price_quote for a stay). It does not explicitly state when NOT to use it versus ot_room or ot_search_rooms, so it falls short of the top band.

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