Кабинет продавца WB: вопросы покупателей

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

Annotations already declare readOnly/idempotent/non-destructive, and the description restates 'Только чтение' (largely redundant), but it adds genuinely new behavioral context: result ordering (newest first) and the required WB_API_TOKEN scope «Отзывы и вопросы». No contradiction with annotations.

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?

Dense and front-loaded with the return contents first, then defaults, then routing, then auth. Every sentence carries information; only the 'Только чтение' clause is redundant against the annotations.

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 compensates by enumerating the returned fields, and it adds ordering, default filtering, mandatory token scope, and the follow-up tool. Nothing essential for correct invocation is 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?

Schema description coverage is 100%, so skip/take/answered are already documented, and the description mostly repeats the answered default rather than adding syntax or format detail. A useful bonus is noting that the returned id feeds wb_seller_answer_question, but this is baseline-level for a fully documented schema.

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?

States a specific verb+resource (list of buyer questions about the seller's products) and enumerates the returned fields (id, date, text, SKU, product name, answer). It also distinguishes itself from the sibling wb_seller_answer_question, which is named explicitly.

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?

Gives the operative default ('По умолчанию — только вопросы без ответа') and routes the agent onward: pass the id to wb_seller_answer_question to reply. Clear context for when to use it, though it does not state explicit exclusions or when not to use it.

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