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

With no annotations, the description should carry the full behavioral burden. It usefully discloses the data source ('from a JSON-RPC node') and the paid/trial gating ('5 free trial calls per signed wallet'), which tells the agent this is a metered read requiring a signed wallet. It omits which chain/node, what happens after the trial, and any rate limits.

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?

A single front-loaded sentence that leads with the verb and resource before the billing aside. The emoji/trial clause is somewhat tangential but compact and informative, with no wasted 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?

For a simple read tool with no output schema and no annotations, the description covers purpose and metering but leaves the chain/network, the response shape, and the undocumented 'input' parameter unaddressed. Adequate but with clear gaps.

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 description coverage is 0% and there are two parameters. The description clarifies only 'address' implicitly; the required-shape 'input' parameter is completely unexplained in both schema and description, leaving one of two params opaque.

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 ('Returns an address's transaction count, the nonce') and even explains the domain term 'nonce'. It is clear what the tool does, though it never names or contrasts against the many sibling read tools (account-age, wallet-balance, rpc, block-number).

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?

There is no when-to-use or when-not-to-use guidance and no named alternative, despite a huge sibling set that includes adjacent on-chain read tools. The only contextual cue is the trial-line, which is about billing, not usage selection.

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