wb_stocks_get

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

With no annotations, the description carries the full burden of behavioral disclosure. It conveys a read operation ('Get'), but does not mention response format, pagination, authorization needs, or any special behavior. This is too thin for a production API tool.

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 a single focused sentence with no filler. The Russian parenthetical is somewhat redundant, but the core information is front-loaded and easy to parse.

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?

There is no output schema and no annotations, so the description should provide more context about return values and invocation behavior. An agent can infer the basic call, but important details around output and parameter meaning are missing.

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?

The phrase 'by barcodes' adds meaning to skus, but the required warehouse_id parameter is entirely unexplained. Schema description coverage is 0%, so the description must compensate for both parameters; it only partially covers one.

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 action ('Get'), a resource ('FBS stock'), and a key input ('by barcodes'), which makes the core purpose clear. It is distinguishable from many siblings such as wb_stocks_update or wb_warehouse_remains, though it does not explicitly name 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?

There is no guidance on when to use this tool versus related stock or warehouse tools. 'By barcodes' weakly implies a use case, but there are no prerequisites, exclusions, or alternative tool references.

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