Yandex Market Search

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

Despite annotations already declaring readOnly/openWorld/idempotent behavior, the description richly discloses real behavioral traits: price_with_plus requires a Yandex Plus subscription, rating_count counts star ratings not reviews, zero results is not an error, and errors are JSON ToolError messages with retryability. No contradictions with 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?

The description is front-loaded with purpose, then uses clear sections for return format and error format. Every paragraph contributes meaningful operational details, and the length is justified by the complexity of pricing and result semantics.

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 search tool with output schema, this description is exceptionally complete: it covers price types, subscription caveats, rating semantics, pagination fields, zero-result behavior, and error handling. An agent has all the context needed to invoke and interpret results without guessing.

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?

The input schema has 100% parameter description coverage, so the baseline is 3. The description adds some context around result pricing semantics but does not materially extend parameter-level meaning beyond the schema's query/page/limit 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?

The description opens with a specific verb and resource ('Search Yandex Market and return products with both prices, ratings and sellers'), clearly distinguishing it from sibling search tools like ozon_search and wb_search. The scope is unambiguous and the tool's role in the marketplace family is evident.

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 frames Yandex Market as the best source for current pricing across the Russian market, including items Wildberries/Ozon do not carry, which guides selection vs alternatives. It also advises preferring price_rub when quoting to a person and directs users to yandex_card for written review counts, providing concrete when-to-use guidance.

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