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

Annotations cover the safety profile, but the description adds context they cannot: malformed addresses return 400 and are uncharged, failed calls are free, and each successful call is billed, which explains why idempotentHint is false despite being a pure read. That pricing/charging behavior is exactly the kind of non-obvious trait an agent needs.

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?

Purpose, alternatives, error behavior, example, pricing and read-only reassurance are packed into a short front-loaded block with no filler. The x402/card-key pricing clause is the only slightly promotional element, though it does carry cost information an agent may need.

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 tool with no output schema, the description covers what is returned (wei and ETH), at what block, what happens on bad input, and the cost model. Nothing needed to invoke it 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 100%, so the baseline is 3; the description goes further by giving a concrete example address and stating that malformed addresses are rejected with 400, which tells the agent what input validation to expect. It stops short of describing format edge cases such as checksum or ENS-name acceptance.

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 precise resource and scope: native ETH balance (eth_getBalance) of a 0x address on Scroll at the latest block, returned in wei and ETH. It explicitly distinguishes itself from scroll_token_balance (ERC-20) and wallet_portfolio (all holdings), so an agent can pick it without opening the schema.

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?

It states the concrete use case ("check whether a wallet can pay gas or a transfer") and names two sibling alternatives with the conditions that select them. There is no ambiguity about when to reach for this tool versus the token-balance or portfolio tools.

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