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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds real value by listing the returned metrics (Ozon Card price, revenue potential/lost revenue, stock, sales, complete product card), but says nothing about data freshness beyond the schema's date params, latency, or cost of a call.

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 sentence that front-loads purpose before the return-field list; no boilerplate or repetition. The field enumeration is long but each item conveys distinct output information rather than padding.

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 field list is the main thing the description must supply, and it does. However, in a crowded family of ~20 Ozon tools, the definition gives no routing advice and doesn't explain how to obtain a valid productId — the remaining gap for an agent to call this correctly.

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 productId, startDate, endDate and includeFbs are already documented. The description only reinforces the 'one product ID, not an array' rule and stays silent on how the date range affects the returned statistics or what includeFbs toggles — correct baseline of 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 ('full detail query' for an 'Ozon Russia SKU') and bounds scope to one product ID per call, plus enumerates the fields returned. It never names the near-duplicate siblings (nexscope_data_mp_ozon_product_detail, nexscope_ozon_product_detail_search, nexscope_ozon_product_search), so the agent must infer which Ozon detail endpoint to pick from naming 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?

The only usage constraint is 'one product ID per call', which hints at batching behavior but not when to choose this over the several other Ozon product detail/search tools. There is no statement of prerequisites (valid SKU source), no exclusion, and no alternative named.

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