Search stays

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description goes beyond that, disclosing the multi-platform fan-out, the Toman (IRT) currency, that price.total is populated only when dates are supplied, and that per-platform failures surface in an 'errors' field while other results still return. That partial-failure behavior is genuinely non-obvious and valuable.

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 sentences, all front-loaded and information-dense: scope, currency, pricing semantics, error handling. Nothing is repeated from the schema and no sentence is 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?

With no output schema, the description must carry return-value context, and it does disclose the price.total/perNight duality and the 'errors' array for failed platforms. It stops short of describing result item shape or ordering/pagination, but covers the quirks an agent most needs.

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. The description only lightly reinforces parameter meaning, clarifying that min/max price are per-night and that dates switch pricing from perNight to total, but adds no syntax beyond the schema's own date-format and enum documentation.

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 (search short-term rentals) plus the aggregation scope across Jabama, Jajiga and Otaghak in Iranian cities. The 'at once' framing and the property-type examples make it unmistakable versus siblings like get_stay, which fetch a single listing.

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 clearly (discovery/search across platforms before drilling into a specific stay), but no alternative is named and no when-not condition is given. There is no pointer to get_stay or get_quote for single-listing or pricing follow-ups.

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