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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered structurally. The description adds nothing beyond that — no note on data freshness, quota/rate limits, or what the keyword-mining results represent.

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 one short sentence, but that brevity reflects under-specification rather than efficiency. Nothing is front-loaded because there is nothing substantive to front-load.

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 21-parameter, nested-object tool with no output schema, the description should carry significant weight. Instead it is a bare API label, leaving an agent with no idea of the result shape, semantics of the mining operation, or how to choose it over the numerous sibling Ozon keyword 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% across all 21 parameters, so the schema itself documents each range object, matchType, and paging structure. Per the high-coverage baseline this lands at 3, but the description contributes nothing about how the filter parameters interact or how keyword mining differs from a plain keyword search.

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/title ('Ozon Intelligence SR: ozon/keyword Mining API') with no verb explaining what the call actually does or returns. An agent cannot distinguish it from siblings like nexscope_data_sr_ozon_market_keyword_search or nexscope_data_sr_ozon_keyword_back_search, which share the same Ozon keyword domain.

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 mention of prerequisites, and no routing to alternatives among the many sibling Ozon keyword tools. The only information is an opaque API path.

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