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

Goes well beyond the annotations: discloses that malformed addresses return 400 and are uncharged, the $0.01/call x402 or credits pricing, the first-25-free allowance, and that repeats are not free (which meaningfully explains the idempotentHint=false annotation). Also reaffirms read-only semantics with concrete consequence ('reads or computes only and changes nothing').

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 purpose and return shape are front-loaded in the first clause, followed by routing guidance, then error/pricing detail. Dense but every sentence carries information an agent would otherwise lack, with no 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, the description still specifies return values (wei and ETH), the state snapshot (latest block), and error semantics. Combined with the single fully documented parameter, nothing an agent needs to call this correctly is missing.

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 already 100%, so the baseline is a 3, but the description adds a concrete example address, clarifies 'any 0x wallet address' (including contracts per the schema), and documents validation behavior for malformed input. That is real added value over the schema.

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 the specific resource (native ETH balance), the underlying method (eth_getBalance), the scope (Arbitrum One, latest block) and the units (wei and ETH). It explicitly differentiates itself from arb_token_balance and wallet_portfolio, so an agent can route correctly among the many sibling balance tools.

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 the concrete decision rule: use this to check gas/transfer funding, use arb_token_balance for ERC-20s, and wallet_portfolio for all holdings at once. This is explicit when-to-use plus named alternatives, the top of the scale.

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