Binance Smart Chain: bscGetBalances

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

Annotations already declare readOnlyHint, destructiveHint false, idempotentHint, and openWorldHint. The description adds valuable detail: it returns native BNB and BEP-20 tokens with contract address, symbol, decimals, and conditional USD pricing, which goes beyond the 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?

The description is a single sentence that is clear, front-loaded with the action, and concise with no wasted words. Every part 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?

Given there are no input parameters and no output schema, the description adequately explains the returned data (native BNB, BEP-20 tokens, field details). However, it does not mention that it uses the authenticated user's wallet or any limitations (e.g., pricing availability).

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?

No parameters exist, so schema coverage is 100%. The description implicitly explains that the tool outputs holdings, adding meaning beyond the empty schema by specifying what is returned and its structure.

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 user wallet holdings on BNB Smart Chain (chain ID 56), specific to native BNB and BEP-20 tokens with details like contract address, symbol, decimals, and USD value. It distinguishes from sibling tools like baseGetBalances and ethGetBalances by specifying the chain.

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 implies this tool is for checking BSC balances but does not provide explicit guidance on when to use it versus alternatives like baseGetBalances or ethGetBalances. No when-not or context for selecting among siblings.

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