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

Annotations already communicate readOnlyHint=true and destructiveHint=false, so the description does not need to state that this is a safe read operation. It adds scoping context ('any BSC wallet address' and two token types) but does not reveal return format, units, or error behavior. This is adequate but not rich.

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?

One short, front-loaded sentence carries all essential information. There is no fluff, repetition, or unnecessary detail.

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 single-parameter, read-only balance lookup, the description plus schema are largely sufficient. The lack of an output schema means the agent must infer the exact response shape, but the description does state what will be returned (BNB and $BOBAI balance), which covers the primary expectation.

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 schema covers the only parameter, 'address', with its format ('0x + 40 hex chars'), so description-level parameter guidance is unnecessary. The tool description adds only the notion of 'any' address, which slightly reinforces that no specific wallet ownership is required.

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 identifies the resource (balances) and the scope (any BSC wallet address), making the purpose easy to grasp. It lacks an explicit verb like 'get' or 'query', but the phrasing is unambiguous and distinct from sibling tools focused on supply, price, liquidity, or NFT data.

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 phrase 'any BSC wallet address' implies that this tool is appropriate for checking balances of arbitrary addresses, which is useful usage context. However, it does not explicitly contrast with sibling tools or state when not to use it, leaving some routing inference to the agent.

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