Поиск отелей

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

Annotations already provide readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds meaningful context beyond that by stating that booking via MCP is impossible and that only search/compare is supported, which clarifies the practical scope.

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 is compact and front-loaded: the core search parameters are presented first, followed by the no-booking restriction and a sibling referral. Every sentence adds value and there is no redundancy.

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?

Given that the tool has an output schema and read-only annotations, the description provides all needed invocation essentials: query semantics, date format, child age format, and the alternative for deeper hotel details. It is complete for correct selection and invocation.

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 0%, but the description compensates by explaining query values, checkin/checkout date format, and children format. It does not explicitly describe adults/limit, but these are inferable from their names and schema defaults, making the parameter guidance strong but not complete.

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?

Description states a clear verb and resource ('Поиск отелей') and explicitly explains what the query accepts (city, region, or hotel name). It differentiates itself from hotel_info by adding that booking is not possible and that price/cancellation details belong to hotel_info.

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?

It explicitly tells the agent this tool is only for finding and comparing hotels, not for booking, and directs specific rate/cancellation lookups to hotel_info(hotel_id, checkin, checkout). This gives a clear when-to-use and when-not-to-use routing.

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