wb_seller_rating

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

No annotations are provided, so the description carries the full burden of disclosing behavior. It does not state whether this is read-only, what exact value it returns, whether the rating is current/cached, or what the response looks like. Very little beyond the tool name is revealed.

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?

The description is extremely short and easy to scan, which is good. However, it is a noun phrase rather than an actionable sentence, and the Russian parenthetical merely duplicates the English phrase without adding useful context.

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?

Because the tool accepts no parameters, an agent cannot misconfigure a call, which lowers the burden. Still, with no output schema and no behavioral notes, the description does not fully specify what the agent should expect when invoking the tool.

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?

The tool has zero parameters, so parameter semantics are trivially satisfied and the description does not need to document inputs. The 100% schema coverage and empty schema mean there is no parameter ambiguity to resolve.

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 names the resource ('seller rating of the shop') and the tool name implies retrieval, so an agent can infer the basic purpose. However, it lacks a verb such as 'get' or 'return', and it does not distinguish this from similar seller-related tools like wb_seller_info or wb_analytics_item_rating.

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 guidance on when to use this tool instead of alternatives, no mention of prerequisites, and no context about what makes it the right choice. The description merely labels the data without explaining its role relative to siblings.

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