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

Annotations already declare readOnlyHint and destructiveHint=false, but the description adds meaningful things beyond them: a $0.01 per-call price, 25 free calls, malformed addresses returning 400 uncharged, and the warning that repeats are not free (consistent with idempotentHint=false). It only stops short of describing the shape of the returned data, which slightly blunts how complete the behavioral picture is.

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 purpose, then usage routing, then pricing and failure semantics, so the most important information comes first. The pricing and credits clause ('$0.01/call via x402 USDC or a card key (/credits), first 25 free') is slightly dense and reads more like billing copy than tool guidance, though it is relevant for a paid endpoint.

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, alternatives, cost, and input validation well. It never says what the response looks like (for example, whether confirmed and pending counts come back as separate fields), which leaves one small gap for a caller that needs to consume 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% for the single 'address' field, so the schema already carries most of the weight and the baseline is 3. The description adds genuine meaning by giving a concrete example address and stating that a malformed address is rejected with 400 without charge, which tells the caller what counts as valid input rather than merely repeating '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?

States a specific verb and resource ('Read the transaction count (nonce) of a 0x address on Linea') and disambiguates scope by noting both confirmed and pending counts. It also names the sibling it is not ('for its balance use linea_balance'), so an agent can distinguish it from linea_balance without opening either 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?

Gives two concrete use cases ('to build the next transaction' and 'to tell whether an address has ever sent anything') and explicitly routes balance lookups to linea_balance. The only guidance a caller might want and does not get is a warning against using it for anything other than Linea, which the name already conveys.

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