Описание и характеристики товара WB

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

The description claims 'full description' (Полное описание) while annotations include openWorldHint=true, which indicates the result may be incomplete or non-exhaustive. This contradicts the annotation, and no other behavioral details beyond the token note are provided.

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 two short sentences, front-loaded with the primary purpose. It is concise and has no fluff, though it could mention the token requirement earlier.

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?

For a simple read-only tool with one parameter and no output schema, the description gives a general idea of the returned data (description, characteristics, composition). However, the contradiction with openWorldHint and lack of detail on response format or pagination make it incomplete.

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%, and the article parameter is already documented with its meaning and source. The description adds no extra parameter semantics, but the baseline for high coverage is 3.

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 returns full product description, characteristics, and composition from the seller card, which is a specific verb+resource. It distinguishes from siblings like price history or reviews by the nature of the data, 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?

The only usage guidance is 'works without token,' which is a prerequisite note. There is no explicit when-to-use instruction or comparison to sibling tools like wb_product or wb_reviews, so the agent must infer when this is the right choice.

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