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

With no annotations at all, the description carries the full behavioral burden. It does convey that this is a passive lookup and that both confirmed and pending balances are returned, which is genuine behavioral detail. It says nothing about whether a malformed or non-mainnet address errors out, whether any address format (legacy/bech32) is accepted, or about rate limits, so gaps remain against a zero-annotation baseline.

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?

Two tight sentences with the payload description front-loaded and the usage hint trailing. Slight deduction because the field enumeration overlaps what the existing output schema already documents, but nothing is padded or meandering.

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 one-parameter read tool with an output schema, the description covers purpose and return shape adequately. It is still missing the input contract (address format/network) and any routing guidance versus siblings like bitcoin_transaction and bitcoin_fees, which an agent needs to invoke it 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?

There is a single required parameter (address) with 0% schema description coverage, so the description must compensate and does not. It never states the expected address format (base58 vs bech32), network (mainnet/testnet), or what happens on an invalid value; the word "Bitcoin address" merely repeats the parameter name.

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 the specific resource (a Bitcoin address) and enumerates exactly what the tool returns: confirmed and pending balance, total received/sent, transaction count, and the latest 10 transactions with net amounts. That is far more concrete than a restated title. It does not differentiate itself from nearby siblings such as bitcoin_transaction or evm_wallet_balance, which keeps it below 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?

"Use to check a BTC payment or wallet" gives an implied usage context, which is better than nothing. However, it offers no exclusions and never points to an alternative when the caller wants a single transaction (bitcoin_transaction), fees (bitcoin_fees), or a non-BTC chain balance. The choice between siblings is left entirely to inference.

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