wb_stats_orders

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

No annotations are provided, so the description bears the full transparency burden. It does disclose a meaningful behavior: the statistics include cancellations. However, it does not state whether this is a read-only operation, how results are aggregated, what period behavior applies, or what the response contains. Some useful context is present, but significant gaps remain.

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 a single short sentence that front-loads the core purpose and adds a targeted use case. The Russian parenthetical is somewhat redundant but harmless. It earns its place with no wasted content.

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 annotations, no output schema, an undocumented required parameter, and ambiguous flag behavior, the description leaves too much unstated. An agent would need external knowledge to call this tool correctly, especially regarding the date_from format and what 'updated only' means.

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 only 50%: date_from has no description and is required, while flag has a minimal description. The tool description adds no parameter-level meaning, so an agent cannot infer the date format, how updated-only filtering behaves, or how cancellations relate to the query parameters.

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 states a clear subject and intent: order statistics, with cancellations included. It is not a tautology and it differentiates itself from sibling stats tools like wb_stats_sales and wb_stats_stocks by naming cancellations and return analysis. It lacks an explicit verb like 'retrieve' or 'get', but the resource and scope are identifiable.

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 phrase 'for cancel and return analysis' gives a clear intended use context. It does not name alternatives or explicitly state when not to use it, so it falls short of a 5, but the context is enough for basic routing.

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