wb_prices_set

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It reveals that prices and discounts are set, but does not explain overwrite behavior, required authentication, side effects, or whether the operation is reversible. For a mutation tool, this is insufficient.

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 brief and front-loaded with the core action. The item shape is stated compactly. The '[P0]' prefix adds minor noise, but overall the text is appropriately short.

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, and only a minimal nested-array schema, the description should provide more operational context. It does not clarify what price format is expected, whether discount is optional, how many items can be sent, or how this differs from related price tools, leaving an agent under-equipped.

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%, so the baseline is 3. The description repeats the schema's '{nmID, price, discount}' structure but adds no extra meaning such as units, discount scale, value constraints, or item-level requirements.

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 uses a specific verb and resource: 'Set prices and discounts' with items identified by {nmID, price, discount}. This makes the core operation clear, though it does not differentiate from the sibling wb_prices_b2b_set.

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 provided about when to use this tool versus alternatives such as wb_prices_b2b_set, wb_prices_list, or wb_prices_club_discount. The '[P0]' prefix appears to be a priority marker, not a usage instruction.

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