WB: get stocks

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

No annotations are provided, so the description carries the full burden. It discloses read-only behavior, the never-merge rule for FBO/FBS, the 30-minute refresh cadence, and the required token category—all key behavioral traits beyond what the schema shows.

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?

Three sentences, all informative and free of fluff. The most critical information, what the tool returns and the FBO/FBS split, is front-loaded, followed by necessary behavior and prerequisites.

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 an output schema and full parameter documentation present, the description covers prerequisites, read-only behavior, data freshness, and the FBO/FBS distinction—everything needed for correct invocation and selection.

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 coverage is 100%, so the baseline is 3. The description adds little beyond the schema's parameter descriptions, though it reinforces the 'never merged' behavior relevant to the fulfillment_model parameter.

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 a specific verb ('Returns'), a precise resource ('current stock levels'), and the key split by FBO/FBS. It clearly identifies this as the Wildberries stocks tool, distinguishing it from sibling tools like ozon_stocks_get and ym_stocks_get.

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?

It provides clear usage context: read-only, requires the Analytics token category, and data refreshes every 30 minutes. It does not explicitly name alternatives or when-not conditions, but the WB-specific scope and prerequisites are strong enough for an agent to know when to select this tool.

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