wb_prices_size_list

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

No annotations are provided, so the description carries the full burden of explaining behavior. It only states the output content and does not disclose whether this is a read-only operation, how limit/pagination works, or what the response shape will be. 'Prices' implies a read operation but does not state it.

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 extremely short and front-loaded, with no filler or redundant detail. The bilingual gloss adds minimal but acceptable redundancy. Incompleteness is penalized in other dimensions, not here.

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?

Given no annotations and no output schema, the description is too thin to fully support invocation. It omits limit behavior, response format, and read-only context. For a low-complexity tool this is below the minimum viable level.

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 0%, so the description must compensate for undocumented parameters. It weakly implies nm_id via 'one product' but says nothing about the limit parameter or its default value. With two parameters and no schema docs, this is insufficient.

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 identifies the resource ('prices per size') and scope ('for one product'), which distinguishes it from sibling tools like wb_prices_list. However, it lacks an explicit verb such as 'get' or 'list', with that action only appearing in the tool name.

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 one product' implies when this tool should be used, and the per-size scope separates it from general price tools. But there is no explicit guidance about alternatives, exclusions, or when not to use it.

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