Кабинет продавца WB: продажи

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

Annotations already mark this read-only, idempotent and non-destructive, and the description adds genuinely new operational context: the exact token scope required (WB_API_TOKEN with «Статистика») and the WB rate limit of 1 request per minute. These are precisely the auth and throttling facts an agent cannot get from 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?

Three tightly packed sentences: what is returned first, then auth requirement, then rate limit. No filler and the highest-value constraint (token scope) is not buried.

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?

With no output schema, the description carries the burden of describing results, and it does name the metrics returned. It stops short of explaining aggregation shape, whether returns are broken out separately, or result size limits, which would matter for an agent parsing the response.

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%, so both date parameters (including their ISO pattern and default windows) are fully documented by the schema. The description only refers generically to «за период» and adds no format or boundary semantics beyond that, 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?

States a specific verb and resource (sales and returns for a period) and enumerates the payload: quantity, buyer payments, seller payout, top SKUs by revenue. This is clearly distinguishable from siblings like wb_seller_orders, wb_seller_stocks or wb_seller_prices without opening any schema.

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?

The description implies period-based reporting and its preconditions (Statistics-scope token), but never states when to choose this over wb_seller_orders or other analytics siblings, nor any when-not condition. Usage is inferable from the resource name rather than stated.

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