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 structurally, and the description adds nothing on top of that. It says nothing about what a back-search returns, whether historical data requires historyDate, rate limits, or data freshness — all relevant for a 26-parameter read query.

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?

It is short with no wasted words, but that brevity is under-specification rather than concision — a single tautological sentence that conveys no actionable information.

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 26-parameter tool with nested paging/sorting objects, range filters, and no output schema, the description provides no orientation at all. An agent cannot tell what the result set contains or how to interpret the many range filter objects.

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 each parameter (skuIds limit of 20, hasVariant semantics, matchType 0/1, type 0/1, historyDate format) is already documented in the schema. The description contributes zero additional parameter meaning, which is the baseline when the schema does all the work.

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 is a restatement of the tool name and title ('Ozon Intelligence SR: ozon/keyword Back Search API') with no plain-language explanation of what a keyword 'back search' actually returns. 'Back Search' is unexplained jargon that does not distinguish this from the many sibling tools such as nexscope_data_sr_ozon_market_keyword_search, nexscope_data_sr_ozon_keyword_mining, or nexscope_ozon_keyword_back_search.

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?

No when-to-use, when-not-to-use, or alternative-tool guidance is given at all. With roughly a dozen near-identical Ozon keyword tools in the sibling list, the absence of any routing hint leaves selection to guesswork.

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