Deals and discounts

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so safety is covered; the description adds real behavioral detail beyond that — the 14:00–23:50 Iran-time display window, undated prices for last-second rooms, and the fact that city filters out last_second entirely. It stops short of describing result shape or pagination, which is acceptable given the output 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?

Front-loads the core purpose ('Current discounts: ...') then details each list, with zero filler sentences. The backtick-heavy, oddly line-wrapped formatting is slightly noisy but not verbose.

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 an output schema present, return values need not be described; the description instead covers the two list modes, their scoping rules, the time window, and the natural next call. Nothing an agent needs to invoke this correctly is missing.

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 adds interaction semantics the schema cannot express: `city` suppresses the last_second list, and supplying dates makes most_discounted prices stay-specific. That is genuine meaning beyond the per-field descriptions.

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 resource (current discounts / deals) and explicitly splits it into two named lists, 'last_second' and 'most_discounted', each with its own scope and sort order. An agent can tell this apart from ot_search_rooms or ot_price_quote 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?

Gives concrete selection conditions: last_second is site-wide and excluded when `city` is supplied, while most_discounted is scoped to the 'discounted' collection and honors city/dates. It also routes the agent forward ('Next: ot_price_quote for the exact total'), though it does not contrast itself against the other room-search siblings.

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