wb_promotions_products

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

With no annotations, the description carries the burden of disclosing behavior. It clarifies that in_action=true means participating and names the returned price/discount fields, which is useful. However, it omits pagination behavior, default filter semantics, and the overall response shape, so transparency is only partial.

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 short and front-loaded with the core purpose, with no filler. The parenthetical Russian phrase is lightly redundant but does not significantly hurt clarity.

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 tool is a simple read/list operation, and the description names key return fields despite having no output schema. It is still incomplete: no pagination expectations, no note about how to find a valid promotion_id, and no relation to sibling promotion tools.

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 50%, covering limit and in_action. The description adds value by decoding in_action ('true = participating'), but it does not compensate for the undocumented promotion_id and offset parameters beyond what their names imply.

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?

Description states the resource (goods eligible for a promotion) and indicates a retrieval operation by mentioning returned fields such as price/planPrice and discount/planDiscount. It distinguishes itself from sibling promotion tools in substance, though it never uses an explicit verb like 'get' or 'list'.

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?

No guidance is given for when to call this tool instead of wb_promotions_list, wb_promotions_details, or wb_promotions_add_products. The description explains the in_action filter but does not specify prerequisites, such as obtaining a promotion_id from wb_promotions_list first, or exclusions.

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