wb_prices_list

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

With no annotations, the description carries the full burden of behavioral disclosure. It only says 'current prices and discounts for all goods,' but does not mention pagination behavior, the effect of limit/offset, or that 'all goods' is constrained by the default limit of 100. The claim of 'all goods' is potentially misleading given the paginated input schema.

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 and is generally efficient. The parenthetical Russian terms add the additional 'маржинальность' (margin) not present in the English text, though there is some redundancy with 'prices and discounts.' No wasted narrative or padding.

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 and no annotations, the description is thinner than needed. It identifies the returned data categories but omits pagination semantics, the meaning of 'all goods' under a default limit, and how filtering by nmID changes the result set. An agent would lack enough context to reliably paginate or interpret partial results.

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 33%, so the description should compensate by explaining parameters. It does not mention limit, offset, or filter_nm_id at all. The schema already documents filter_nm_id, but the description adds no meaning to the pagination parameters or how filtering interacts with the 'all goods' claim.

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 that the tool exposes current prices, discounts, and margin for all goods, which clearly identifies the resource and data scope. It stops short of an explicit verb like 'returns' or 'lists', but the tool name and content make the purpose reasonably clear, and it is distinguishable from sibling price tools like wb_prices_set and wb_prices_quarantine.

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?

There is no guidance about when to use this tool instead of alternatives such as wb_prices_set, wb_prices_upload_status, or wb_prices_size_list. The description gives no context for choosing it, no exclusions, and no mention of typical use cases or prerequisites.

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