Кабинет продавца WB: заказы

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

Annotations already declare it read-only, idempotent and non-destructive, so the safety profile is covered. The description adds genuinely useful context beyond that: the required token scope («Статистика») and the WB rate limit of one request per minute, both of which affect call behavior.

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?

Two tight sentences: the first front-loads what the tool returns, the second carries the prerequisites. No filler. Could be marginally better only by adding the sibling contrast, which is not a conciseness issue.

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 compensates by enumerating the returned metrics, and it covers auth scope and rate limits. For a simple two-optional-date read tool this is largely complete; only the absence of sibling routing guidance is a minor gap.

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% — both date_from and date_to, their format pattern, and the default (7 days back) are already documented in the schema. The description only gestures at 'за период' and adds no syntax or default detail beyond what the schema provides, so the baseline of 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+resource ('Заказы продавца за период') and enumerates the returned metrics (count, sum, cancellations, daily breakdown, top SKUs), which meaningfully distinguishes it from siblings like wb_seller_sales. However, it never explicitly names which sibling to prefer over this one, so differentiation is implicit rather than stated.

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 'за период' framing and the WB_API_TOKEN («Статистика») prerequisite imply the usage context, and the 1-req/min limit tells the agent when it can call. But there is no explicit when-to-use guidance or contrast against alternatives such as wb_seller_sales, leaving the agent to infer the choice.

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