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

Annotations supply only readOnlyHint=false and openWorldHint=true, which signal an external call but say nothing about scope, data freshness, or cost. The description adds zero behavioral context of its own — no mention of what the `historyDate` window means for freshness, rate limits, or whether results are attributed to a memberId.

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 only one sentence, but that is under-specification rather than conciseness — the single line is a title echo with no actionable front-loaded 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 tool with 26 parameters, three required inputs, nested range objects, and no output schema, a bare title restatement leaves the agent with essentially no information about results, defaults, or constraints. The description is completely inadequate for this complexity.

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% across all 26 parameters, so the schema already carries the semantic burden and the baseline of 3 applies. The description contributes nothing beyond that — it does not explain the interaction between skuIds, the mandatory hasVariant flag, or how the many `*range*` objects are shaped.

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 title and tool name: "Ozon Intelligence SR: ozon/keyword Back Search API." It never states in plain language what the tool actually returns or does (e.g. reverse-lookup keywords that a given SKU ranks for), so the purpose must be inferred from the token "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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives, despite many close siblings (nexscope_ozon_keyword_mining, nexscope_ozon_market_keyword_search, nexscope_data_sr_ozon_keyword_mining, nexscope_ozon_product_report_search) that an agent could easily confuse with this one.

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