marketplace_search

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

No annotations are provided, so the description carries full burden. It mentions normalized results and implies that multiple queries are needed for coverage. However, it does not disclose pagination, sorting, rate limits, or whether the search is case-sensitive.

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?

Two sentences, both meaningful: first states purpose, second gives usage advice. No fluff, but could be slightly more structured with parameter details.

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 moderate complexity (6 params) and presence of output schema, the description covers main purpose and usage strategy but lacks parameter documentation and behavioral details like pagination or result ordering.

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%, and the description does not explain any of the 6 parameters. Only 'brand' is hinted at via 'с брендом'. The agent must rely on parameter names alone, which may be insufficient for correct invocation.

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 clearly states searching for products on Ozon and/or Wildberries with normalized output. It uses specific verbs and resources, distinguishing it from siblings like get_product_card and get_reviews.

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?

Provides explicit guidance to formulate multiple queries with different brands and formulations for better coverage, and to compare results. While it doesn't explicitly mention when not to use or name alternatives, the strategy is clear and useful.

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