wb_finance_balance

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

With no annotations provided, the description carries the burden of behavioral disclosure. It usefully reveals the auth scope (Finance category) and the semantic components ('payable, in transit'). However, it does not explicitly state that this is a read-only operation or describe any response behavior, which would be helpful for a balance endpoint.

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 very short and front-loaded with the core resource. The '[P0]' prefix is internal priority noise and the parenthetical Russian translation adds slight redundancy, but otherwise every phrase earns its place.

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, the description is mostly adequate: it names the resource, the balance components, and the required token category. However, with no output schema and no usage guidance, an agent may still be uncertain about the exact response shape or when to choose this over related finance tools.

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 is empty with zero parameters, so there is no parameter burden for the description to carry. The description adds semantic context about what the balance covers, which is the relevant information an agent needs.

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 names a specific resource ('Seller balance') and its key components ('payable, in transit'), which clearly identifies what this tool is about. It lacks an explicit verb like 'get' or 'retrieve', but the noun 'balance' in an API context strongly implies a read operation. It is somewhat distinguishable from siblings like wb_advert_balance by the 'Seller' qualifier and Finance category note.

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 about when to use this tool versus alternatives such as wb_finance_report, wb_finance_acquiring_list, or wb_advert_balance. The only conditional information, 'Token needs the Finance category,' is an authorization prerequisite rather than usage guidance.

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