Get price quote

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

Annotations already declare readOnlyHint, and the description reinforces it with 'Read-only: nothing is booked'. It then adds context the annotations cannot: that fees/extra-guest charges appear only 'where the platform reports them' and that Otaghak quotes are calendar-derived estimates (estimated: true). That provenance caveat is genuinely useful behavioral disclosure.

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 sentences, front-loaded with the purpose and price semantics, followed by the read-only guarantee and the estimate caveat. No filler; every clause carries information.

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 does the work of describing the return qualitatively — exact price in Toman, inclusion of extra-guest charges and fees, and an estimated flag — which is close to complete for a read-only quote tool. It could go further on how unpriced or unavailable platforms are surfaced, but the core is covered.

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 id, guests, checkIn and checkOut (including the Jalali/Gregorian date flexibility) are fully documented in the schema. The description adds no syntax or constraint 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?

States a specific verb+resource: exact price (in Toman) for one stay, scoped to dates and guest count. The currency, the inclusion of extra-guest charges and fees, and the 'one stay' scope make it distinguishable from get_stay and search_stays without opening schemas.

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 — compute a price for a given stay and date range — and the 'nothing is booked' note clarifies it isn't a booking step. However, no sibling is named and no when-not condition is given, so an agent must infer the boundary versus get_stay itself.

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