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

The description usefully discloses scope (single ID per call, arrays rejected) and enumerates what comes back, including derived metrics like revenue potential and lost revenue. It does not address data freshness, auth/permission requirements, rate limits, or cost, which matters because annotations only supply openWorldHint=true and a readOnlyHint=false that reads as inconsistent with a pure data query and is left unexplained.

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?

A single front-loaded sentence that leads with platform, scope, and cardinality before the field list. The long return-field enumeration is dense but justified given there is no output schema, and no sentence is filler.

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?

Because there is no output schema, enumerating the returned fields (price, discount, Ozon Card price, rating, reviews, stock, sales, revenue, listing date, images, product card) is genuinely necessary and present. The remaining gap is that it never explains how the date-range parameters shape those statistics, nor how this differs from the other Ozon detail endpoints.

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 all four parameters are already documented, and the description only reinforces the non-array constraint on productId. It says nothing about the startDate/endDate statistics window, even though the returned sales/revenue figures clearly depend on those dates, so it adds little 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?

The description gives a specific verb+resource ("full detail query" for an Ozon Russia SKU) and explicitly scopes it to "one product ID per call," which separates it from search-style siblings. However, it does not distinguish itself from the near-identical `nexscope_data_mp_ozon_product_detail` or `nexscope_ozon_product_detail_search`, so an agent cannot tell those apart from the text 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?

Usage is only implied: fetch this when you already have a single Ozon product ID and need the full card. There is no explicit statement of when to prefer it over `nexscope_ozon_product_search` (find an ID first) or over the other Ozon detail tools, and no prerequisites or exclusions are mentioned.

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