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

Annotations supply openWorldHint=true and readOnlyHint=false; the description adds the returned metric set, AND-combined numeric filters, sorting, and currency conversion, which is useful context beyond the annotations. However, it never addresses pagination behavior, why a pure query tool is marked non-read-only, or rate/row limits. No explicit contradiction, but the description's read framing sits uneasily with readOnlyHint=false.

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 sentence front-loads the purpose, but the trigger list is bloated and repetitive – 'Ozon seller drill-down' appears twice, and several triggers ('Ozon seller products', 'Ozon seller SKUs') restate each other. The keyword dump crowds out the more valuable behavioral detail.

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 15-parameter read/query tool with no output schema, the description covers what is returned (sales, revenue, price, rating, stock, turnover, lost revenue) and the analysis use cases, which is enough to call it. It omits paging guidance and the sellerId sourcing constraint beyond the schema's own text, leaving modest gaps.

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 parameter including filters[].op/field/value/value2, sortField, and currencyRate is already documented in the schema. The description only gestures at 'multi-dimensional numeric filters, sorting, and currency conversion' without adding syntax or format detail, which matches 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?

States a specific verb and resource: returns all SKUs under an Ozon seller ID with a named set of metrics. It is clear what the tool produces, but it never distinguishes itself from the near-identical sibling nexscope_data_mp_ozon_seller_products or from nexscope_ozon_product_search, so an agent cannot tell which to pick from the description alone.

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 concrete usage contexts (store structure analysis, seller bestseller analysis, competitor store benchmarking) and a long list of trigger phrasings, including the fallback rule about intents that never mention Nexscope. It stops short of any when-not-to-use guidance or named alternatives, so the routing is keyword-driven rather than decisive.

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