WB: list orders

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

With no annotations provided, the description carries the full behavioral burden. It discloses that the operation is read-only, that data refreshes every 30 minutes, and that data is retained for 90 days. It does not mention pagination or rate limits, but for a read-only listing tool the disclosed behavior is substantially informative.

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 three sentences with no filler. It front-loads the core purpose, then adds the read-only behavior and a practical usage recommendation. Every sentence earns its place.

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?

The description is adequate for a simple first call, and output schema likely covers return values, but it omits pagination entirely. Since limit defaults to 100 with a maximum of 200, the recommendation to use this tool for aggregate sales stats is incomplete without telling the agent to paginate via cursor.

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%, and the description adds no parameter-level meaning beyond what the schema already states. The '30 days by default' and '90 days' language merely restates the date_from schema description, while limit and cursor remain undocumented in both the schema and the description.

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 specific verb ('Returns'), a specific resource ('Wildberries orders'), and enumerates the returned fields (date, article, amount, warehouse, status). It also distinguishes this from sibling tools by explicitly naming Wildberries and positioning it as the tool to use for order data rather than products, stocks, or prices.

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 gives clear context: it is for reading orders over a period, with a default of 30 days, and explicitly says 'For aggregate sales stats, call this tool and compute on the AI side.' It does not explicitly describe when to use other tools, but its Wildberries-specific scope and the aggregate-stats recommendation provide sufficient guidance for routing.

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