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

The description discloses what each result row carries (search volume, growth, market space, competitor/seller counts, average price, cart-add conversion, top products, market profile), which is valuable since there is no output schema. However, it describes a pure read/search while annotations declare readOnlyHint=false, an inconsistency worth noting (I stop short of calling it a hard contradiction since the description makes no write claim), and it says nothing about rate limits, auth/memberId requirements, or result limits.

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 first two sentences are well front-loaded and informative, but the remainder is a keyword-stuffed trigger list with near-duplicates ('Ozon keyword selection' appears twice, 'blue-ocean keyword mining'/'blue ocean keywords Ozon', 'Ozon keyword research'/'Ozon market keyword search'). Several sentences do not earn their place, diluting the actionable content.

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 24-parameter, nested-object search with no output schema, the description does supply the return-shape summary an agent needs and states the platform scope (Ozon plus Wildberries). Gaps remain around pagination limits and how the many range filters combine, but the critical context is present.

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% and every one of the 24 parameters is documented in the schema (ranges, matchType 0/1, searchDate semantics, page.orders), so the schema carries the burden. The description only restates the metric families as filterable dimensions, adding mild orientation but no syntax or format detail beyond the schema.

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?

States a concrete verb and resource ('filters Ozon (and Wildberries) market keywords') plus the dimensions it filters on, which is enough to distinguish it from generic searches. It does not, however, contrast itself with close siblings such as nexscope_ozon_keyword_mining or nexscope_ozon_keyword_back_search, leaving the agent to infer which Ozon keyword tool applies.

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?

Gives clear usage contexts ('Ozon keyword selection, blue-ocean keyword mining, and market opportunity analysis') and an explicit trigger list, including a no-brand-mention trigger that supports implicit invocation. It never states when NOT to use it or names an alternative sibling, so there is no exclusion guidance.

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