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

Annotations already carry readOnlyHint=true, destructiveHint=false, openWorldHint=true. The description adds genuinely new context beyond them: per-call billing via x402 USDC or a card key, the first 25 calls free, and 'repeats are not free', which concretely explains the idempotentHint=false. The 'changes nothing' sentence is redundant with the annotations but not harmful.

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 returned fields and purposes are front-loaded, and the example and billing model follow in a compact second half. Every clause is relevant, though the pricing/marketing tail is slightly padded for a description whose primary job is invocation instructions.

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?

No output schema exists, and the description compensates by enumerating the returned fields (confirmed balance, unconfirmed pending, totals, transaction counts). Combined with the example address and the cost semantics, an agent has what it needs to call and interpret the result.

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 coverage is 100% and there is only one parameter, so the schema carries most of the weight. The description still adds value by spelling out which address families are accepted (legacy, P2SH, bech32) and providing a concrete bech32 example, which helps the agent validate its input.

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?

States a specific verb+resource: 'Balance and activity of any Bitcoin mainnet address (legacy, P2SH or bech32)'. It also enumerates exactly which numbers come back (confirmed balance in sats/BTC, unconfirmed pending, total received/sent, transaction counts), so it is unmistakably distinct from siblings like btc_fees or eth_balance.

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?

Gives clear usage contexts: payment verification, checking whether a deposit arrived, and wallet monitoring. It never names an alternative tool or a when-not-to-use condition, so it earns a 4 rather than a 5, but the intended scenarios are explicit enough to route an agent correctly.

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