Товар Wildberries по артикулу

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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses that no token is required and that products not on sale are excluded from the response. It also enumerates the returned data fields, adding real behavioral context.

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?

Two tight sentences: the first lists the returned data, the second adds auth and filtering caveats. There is no filler or repetition.

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 no output schema, the description carries the burden of describing return content, and it does so with a clear field list and an important exclusion rule. For a single-parameter read-only tool this is largely complete, though explicit error or invalid-article behavior is not mentioned.

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 input schema already covers the only parameter fully with a clear explanation of nmId and a URL example. The description's 'по артикулу' just restates the schema, so it adds little beyond the 100% schema coverage.

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 exactly what the tool returns (price, discount, rating, review count, seller, stock, delivery time) for one or more Wildberries products by article. The resource and scope are clear, and the field list implicitly distinguishes it from sibling tools like wb_price_history or wb_reviews.

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 description gives useful context such as 'works without a token' and notes that unavailable products are omitted, but it does not explicitly say when to choose this tool over siblings like wb_product_details or wb_compare. Usage is implied rather than stated.

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