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

Annotations already declare readOnly, openWorld and non-idempotent, but the description adds context those don't: malformed addresses are rejected with 400 and uncharged, failed calls are free, each successful call costs $0.01 with 25 free, so repeats are not free. That pricing/repeat-charge note usefully reinforces idempotentHint=false. It stops short of describing the response shape or rate limits, keeping it below a 5.

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 and scope are front-loaded, followed by usage, sibling routing, error behavior and pricing. It is dense but nearly every clause carries information; the pricing tail is the least essential but still affects call decisions.

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 no output schema, the definition covers purpose, usage, alternatives, error behavior and cost. It implies but never explicitly states that the result reports confirmed and pending counts separately, which is the one remaining ambiguity an agent might hit.

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 the single parameter is required, so the baseline is 3. The description adds a concrete example address and states the rejection behavior for malformed 0x input, giving slightly more than the schema's bare "0x address".

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 opens with a specific verb and resource ("Read the transaction count (nonce) of a 0x address on Ethereum") and states scope (confirmed plus pending). It names the confusing sibling eth_balance explicitly, so an agent can separate nonce from balance without opening schemas.

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 gives two concrete use cases (building the next transaction, checking whether an address has ever sent anything) and routes the balance question to eth_balance. Both when-to-use and the alternative are explicit.

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