wb_buyer_chats

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does reveal two traits: the response includes a replySign usable for answering, and chats may contain complaints or IP-holder claims. But it does not disclose whether this is a read-only fetch, whether it returns a list or a single chat, pagination behavior, or side effects. The replySign hint is useful but underdeveloped.

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 efficient sentence that front-loads the resource and the key answering hook before the content caveat. The Russian parenthetical 'чаты с покупателями' is redundant with the English name, which is minor waste, but overall the length is appropriate for a zero-parameter tool.

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 zero-parameter tool with no annotations and no output schema, the description should clarify the return shape and the replySign workflow. It does not state whether the tool returns a list of all buyer chats, how replySign should be consumed (e.g., passed to wb_chat_send), or how complaints/IP claims should influence handling. An agent has to guess the basic contract of the call.

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 tool has zero parameters and empty schema, so the baseline of 4 applies — there is nothing for the description to document. The replySign mention refers to output content, not an input parameter, so no parameter information is missing.

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 identifies the resource (buyer chats) and a distinguishing feature ('includes replySign for answering'), which separates it from general chat tools like wb_chat_events. However, there is no explicit verb — the tool name is a plural noun implying list retrieval, but the description never states what operation it performs. It reads more like a content annotation than a functional definition.

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?

No guidance is given on when to use this tool versus closely related siblings such as wb_chat_send, wb_chat_events, or wb_chat_download. The description hints at the replySign being used 'for answering' but never states the relationship to wb_chat_send or when this tool should be selected over the alternatives.

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