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

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description adds value beyond them by specifying the required token scope ('Статистика') and the WB API rate limit of 1 request per minute. It also outlines what output aggregates to expect (quantity, amount, cancellations, daily breakdown, top articles). No contradiction with 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?

The description is two sentences with the purpose front-loaded in the first sentence and operational constraints in the second. Every sentence provides essential information without filler, making it highly concise and well-structured.

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 no output schema, the description covers the purpose, the returned metrics, the required authentication, and the rate limit. It does not explicitly mention default date behavior or pagination, but these are either in the schema or not critical for a summary tool. Overall, it is sufficiently complete for an agent to call it correctly.

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% and both date parameters are already documented in the input schema with format and defaults. The description only refers to 'за период' (period) and does not add meaning beyond the schema, so it meets the baseline of 3.

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 clearly states the tool retrieves seller orders for a period with specific metrics (quantity, sum, cancellations, daily breakdown, top articles). It names a distinct resource ('Заказы продавца') but does not explicitly differentiate from the sibling tool wb_seller_sales, so it is clear but lacks sibling differentiation.

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 usage for retrieving seller orders over a period and provides necessary prerequisites (WB_API_TOKEN with 'Статистика' scope) and the rate limit (1 request per minute). However, it does not explicitly say when to use this tool versus alternatives like wb_seller_sales, nor does it state when not to use it.

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