Hotels

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

The annotations already establish a read-only, idempotent, non-destructive open-world operation. Beyond that, the description discloses total-stay pricing in Toman, the meaning of price_per_night_toman, parity with the site's list and count, and possible multi-second latency while hotels respond.

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?

The description front-loads the purpose and follows it with a compact example, pricing semantics, source consistency, and latency. Each sentence contributes actionable information without substantial repetition or unnecessary wording.

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 an eight-parameter search with fully documented inputs, the definition supplies enough context to select and invoke the tool and interpret its core prices. Listing result attributes partly compensates for the absent output schema, though explicit sibling differentiation and any important availability or freshness limitations would make it more complete.

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 the structured input documentation already does most of the work. The example usefully shows several parameters working together, but it adds little input syntax or constraint information beyond the schema; the pricing clarification primarily concerns output fields.

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?

The opening sentence gives a specific verb and resource—searching hotels in a city—and identifies key result attributes such as stars, rating, meal plan, and perks. Domestic and international scope is stated, but the description does not explicitly distinguish this tool from the potentially overlapping al_stays or al_stay_detail siblings.

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?

The explicit 'Use for' example provides a concrete natural-language request involving a city, star preference, stay length, and Jalali date. This gives clear selection context, although there is no when-not guidance or routing to an alternative sibling.

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