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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds genuinely useful payload detail (per-keyword volume, growth, market space, seller/competitor counts, top products, organic/ad rank/exposure/conversion profiles), but says nothing about auth, quotas, or result caps beyond the 20-SKU input limit.

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 opening two sentences are dense and front-loaded with the core operation and return payload. However, the trailing trigger-phrase block is keyword stuffing that restates 'Ozon keyword reverse lookup' in seven near-identical forms plus a redundant 'also trigger when...' sentence, diluting the signal.

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 29-parameter, no-output-schema tool, the description does the important work: it names the required SKU input, the 20-item cap, the filter dimensions, and the fields returned per keyword. It leaves the nested pagination/sorting object and the market-profile structure to the schema, which is acceptable given full schema coverage.

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%, so every one of the 29 parameters is already documented in the schema. The description enumerates the same filter dimensions (volume, growth, product/seller/competitor counts, ranks, exposure, conversion) and repeats the 20-SKU cap, adding no syntax or constraint detail beyond the structured fields — baseline 3.

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 specific verb and resource: reverse-looks up Ozon (and Wildberries) search keywords from a list of up to 20 product SKUs, returning organic/ad search terms. The SKU-driven 'reverse' framing implicitly distinguishes it from forward keyword tools, but no sibling (e.g. nexscope_ozon_keyword_mining, nexscope_ozon_market_keyword_search) is named to make the boundary explicit.

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: listing keyword optimization, competitor traffic word mining, ad keyword analysis, plus an intent-based fallback trigger. It never states when NOT to use it or which sibling to prefer for forward keyword research, so the routing guidance is clear but not complete.

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