Special offers

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

Annotations already cover read-only/idempotent/open-world, and the description adds genuinely new behavioral context: these pages carry no dates, price_from can change, and it is null when the site lists no price (derived from tomorrow's search when free rooms exist). That is real snapshot semantics the agent could not infer from annotations.

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 the resource and the three variants, then the caveats. Compact overall; the parenthetical about tomorrow's search is dense but earns its place by explaining the null case.

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?

For a 3-parameter read tool with no output schema, this covers the important gaps: no dates on these pages, price_from semantics and null behavior, and the handoff to eg_rooms. Only the limit/pagination behavior is absent.

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 67% and the kind enum is already self-documented, so the description mainly restates the city/kind dependency. It does add meaning for the returned price_from field, which is useful given no output schema, but leaves the limit parameter entirely undiscussed.

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 and resource ('List hotels on one of the site's offer pages') and enumerates the three offer kinds, which maps directly to the kind enum. It does not, however, distinguish itself from the sibling eg_deals, which an agent could easily confuse with this 'latest discounts' page.

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 use-case phrasings ('hotels with free cancellation in Shiraz', 'any one-night offers') and an explicit next step ('Follow up with eg_rooms for dates'), so the agent knows this is a discovery step, not a booking/availability call. No explicit exclusion versus eg_deals or eg_search.

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