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

Annotations declare readOnlyHint=false and openWorldHint=true, but the description supplies no behavioral context at all — no auth/permission requirements, no rate limits, no note on what the pagination cap of 20 implies, and no indication of why a search is flagged non-readOnly. It neither contradicts nor enriches the annotations.

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 as short as possible with no waste or filler, but the brevity comes from under-specification rather than from tight writing — there is no front-loaded explanation of what a shop search actually returns.

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 four-parameter tool with a nested paging/sorting object, required seller ID semantics, and no output schema, a one-line title restatement leaves the agent with almost no information for correct invocation or result interpretation.

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 detailed docs for id (negative = self-operated, positive = third-party), the nested page/{page,pageSize,orders[]} object, and the errcode 1002 pageSize limit. The description adds nothing 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 is essentially the title restated: 'Ozon Intelligence SR: ozon/shop Search API.' It does convey that this searches Ozon shops, but adds no verb-level detail about what a 'shop search' returns or how it differs from siblings like nexscope_ozon_seller_products, nexscope_data_mp_ozon_product_search, or the duplicate nexscope_ozon_shop_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 is named. An agent must infer from the word 'shop' and the required sellerId/page params that this is for looking up sellers, with nothing to distinguish it from the many other Ozon and marketplace search tools in the sibling list.

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