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

The description repeatedly frames the tool as a read ('fetches the product list'), yet the annotations declare readOnlyHint=false, implying a mutating/non-read operation. That is a direct contradiction between the description and the structured signal, and the agent gets no resolution of which is true. The otherwise useful disclosure of returned fields (FBO/FBS, seller type, return/cancellation rate, shop totals) does not cure the conflict.

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 core purpose and returned fields are front-loaded in the first sentence, which is good structure. But the tail is a bloated, repetitive trigger list — 'competitor shop analysis' and 'Ozon shop search' each appear twice, and nine near-synonymous phrases pad the length without adding discriminative power.

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?

With no output schema, the description compensates well by enumerating the per-product and shop-level fields returned. Pagination limits, sort fields, and the ID-sign convention are covered by the schema, so the only real gap is the unresolved read-only question raised by the annotations.

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 the schema itself already explains the key subtleties (negative IDs = Ozon self-operated sellers, pageSize max 20, errcode 1002). The description adds only the phrase 'by shop ID' and the notion of shop-level totals, so it stays at the baseline for a fully documented 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?

The opening sentence names a specific verb (fetches) and resource (product list of an Ozon shop/seller) plus the keying parameter (shop ID), and enumerates the returned fields, so the agent knows exactly what it gets. It never names the suspiciously similar siblings (nexscope_ozon_seller_products, nexscope_data_mp_ozon_seller_products, nexscope_ozon_product_search), so the agent cannot tell from the description which of those near-duplicates to prefer.

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 gives clear use contexts — competitor shop product analysis, bestseller mining, seller product structure analysis — and a long list of trigger phrasings including 'even without explicitly mentioning Nexscope'. There is no when-not guidance and no explicit routing away from the near-identical sibling tools, so the guidance is clear but not exhaustive.

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