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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It fails to mention whether the tool is read-only, any rate limits, input format requirements, or how results are paginated. For a wallet query tool, this lack of transparency is a significant gap.

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, concise sentence that front-loads the core functionality ('BNB balance, recent transactions'). Every word earns its place, and there is no redundancy or filler.

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 and no annotations, the description must explain return values and side effects, but it only provides a high-level summary. The tool is simple, but missing details like transaction count limits, order, and the exact response structure make it incomplete for an agent to invoke and interpret results reliably.

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 0%, and the description does not explicitly explain the 'address' parameter beyond implying it is the wallet address. It does not specify address format (e.g., BEP-20), requiredness, or how the parameter relates to the output. This is insufficient for an agent to construct valid inputs confidently.

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 the tool provides BNB balance and recent transactions for a wallet, which is specific and informative. It distinguishes from sibling tools like bnb_overview or bnb_gas by focusing on wallet-level intelligence. However, the word 'intelligence' is slightly vague, so it doesn't fully achieve a 5.

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?

There is no guidance on when to use this tool versus alternatives. No mention of prerequisites, use cases, or exclusions. Given sibling tools like bnb_overview or bnb_token_risk, explicit guidance would be helpful but is entirely absent.

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