wb_prices_upload_status

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It conveys a non-mutating status query and explains the buffer flag for deferred uploads, but it does not explicitly state that it has no side effects or describe what status values are returned.

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. The Russian parenthetical is redundant but does not meaningfully 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 invocation path is mostly covered: upload_id, buffer behavior, and details flag. However, with no output schema and no annotations, the agent is left to guess what the returned status payload contains and which statuses to expect, which is a notable gap for a status-checking tool.

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 documentation covers only details (33% coverage), so the description adds needed meaning: it clarifies that upload_id comes from wb_prices_set and explains when buffer=true is relevant. This goes beyond the raw schema and helps an agent provide the right inputs.

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 clearly states it retrieves the status of a price upload keyed by upload_id from wb_prices_set. This distinguishes it from price-setting or price-listing tools, though it does not explicitly name sibling alternatives.

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 'from wb_prices_set' and 'buffer=true for deferred uploads' implies this is used after a price upload to check its processing status. However, there is no explicit guidance on when to choose this over related tools like wb_prices_list or wb_prices_quarantine.

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