Price 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 new behavior: the result is one row per night, priced in Toman, and sold-out nights are represented as 'sold out' rather than omitted — a detail an agent could not 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?

Three short front-loaded sentences, the core capability first, then the return shape, then the sibling redirect. Nothing is redundant with the schema or annotations.

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 covers the return shape (one row per night, price in Toman, sold-out marker) and the date-range/pagination semantics are implicitly handled by 'days' and 'from_date' in the schema. A brief note on maximum range would be the only missing piece.

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% and the schema already documents days, hotel, and from_date including formats and defaults. The description adds no parameter-level detail beyond that, so the baseline of 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?

Opening line gives a specific verb and resource ('Show the cheapest bookable room price per night over a date range'), including the aggregation logic (cheapest bookable per night), which immediately distinguishes it from listing tools like eg_rooms or eg_hotel.

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?

Explicitly routes the alternative case away ('Full list for one stay: eg_rooms'), which tells an agent when not to use this tool. It does not address when eg_tour_calendar or eg_deals would be preferred, so a small gap remains, but the primary confusion risk is resolved.

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