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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so the safety profile is covered by structured data. The description adds nothing beyond that — no note on auth/member context, no indication of what a shop search returns, and no caveats about the nested paging object. No contradiction, but zero incremental value.

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 a single short sentence with no waste, but that is under-specification rather than conciseness — the sentence carries no information an agent could act on. Nothing is front-loaded because nothing is stated.

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 a nested paging/sorting object, required store ID, and no output schema, the description supplies none of the context needed to call it confidently. An agent must reverse-engineer the tool's behavior entirely from the schema and the endpoint-path name.

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%, including the important detail that negative `id` values mean self-operated sellers and that `pageSize` above 20 returns errcode 1002. The description contributes no parameter meaning beyond the schema, so the baseline 3 applies.

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 restates the title verbatim ("Ozon Intelligence SR: ozon/shop Search API") and never says in plain language what the tool returns or searches over. "Search" is the only verb, and "ozon/shop" is an internal endpoint path rather than a described resource. An agent cannot distinguish this from nexscope_ozon_shop_search or nexscope_data_mp_ozon_seller_products using the description 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?

There is no when-to-use, when-not-to-use, or alternative named. With dozens of near-identical Ozon siblings (ozon_shop_search, ozon_seller_products, mp_ozon_seller_products), the absence of any routing guidance leaves selection entirely to guesswork.

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