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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, so safety is largely covered. The description still adds genuinely non-derivable context: the x402/card-key pricing model, that malformed input returns 400 uncharged, that failed calls are free, and that repeated calls are billed (which explains idempotentHint=false on a pure read). It does not describe the response shape beyond units.

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?

Front-loaded with the operation and chain, then alternatives, then error/cost behavior. Dense but nearly every clause carries information. The billing detail is slightly verbose relative to a single-purpose read tool, keeping it just below a 5.

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 full annotation and schema coverage, the description covers purpose, alternatives, error semantics, side effects and cost. The only gap is return-value structure (field names beyond 'wei and ETH'), which is minor given no output schema.

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?

Only one parameter and schema description coverage is 100%, so the schema already documents 'address'. The description reinforces the expected format ('any 0x wallet address', with a concrete example), but adds no constraint the schema lacks, so the baseline applies.

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 pair (native ETH balance via eth_getBalance) bound to a specific chain (Ink) and block tag (latest), plus return units (wei and ETH). It explicitly distinguishes itself from ink_token_balance and wallet_portfolio, so an agent can pick it without opening siblings.

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 a concrete decision rule: use to check whether a wallet can pay gas or a transfer; for ERC-20 use ink_token_balance; for all holdings use wallet_portfolio. Both alternatives are named with the condition that selects them.

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