Поиск заведений

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

With no annotations, the description carries full burden and excels: it discloses default open-only behavior, that closed venues are hidden, warns not to propose or add to cart closed venues, and that set_address is required. Delivery price is noted as conditional ('if recognized').

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?

Well-structured with a clear purpose sentence followed by scannable bullets. Every bullet conveys a distinct, important guideline; no filler or 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?

Despite no output schema, the description covers all critical behaviors: return contents, query logic, type filtering, open/closed defaults, includeClosed option, and prerequisite address. It is complete for an agent to invoke correctly.

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 75% (limit lacks description), but the description adds significant meaning: query empty vs filled, type restaurant/shop defaults, and includeClosed toggle behavior. These go well beyond the schema's property 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?

The first sentence clearly states the tool returns establishments delivering to the current address, with rating and delivery time. This specific verb+resource+scope distinguishes it from siblings like search_products and get_menu.

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?

Bullet points give explicit when-to-use guidance: omit query for general catalog, use query only for specific searches, use type to separate restaurants/shops, and require set_address. It also warns against inventing keywords and against interacting with closed venues.

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