chainpeek: an account's transaction count (nonce) on Ethereum, Base or Robinhood Chain

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

Annotations already declare read-only, idempotent, non-destructive, open-world, but the description adds substantial operational context beyond them: 30 s RPC caching, 422 validation errors issued before payment, no charge on bad input, sub-1s typical latency, price and free-tier limits, and what 'pending' actually reflects (mempool).

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-loads purpose and sibling routing in the first two sentences, then layers behavioral and commercial details compactly. The pricing/rate-limit/docs tail is dense but each clause carries information; only minor trimming is possible.

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?

An output schema exists, so return-value documentation is not required, yet the description still names the returned fields (nonce, nonce_hex). Combined with chain scope, validation behavior, cost model, and latency, an agent has everything needed to call it correctly.

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 100%, so the schema already documents every parameter including the block enum's mempool semantics and the address pattern. The description largely restates the 'pending' behavior rather than adding new parameter guidance, so baseline 3 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 (get) and resource (an account's transaction count / nonce), names the three supported chains, and explicitly distinguishes itself from transfer_preflight and get_block_number. An agent can identify the right tool 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?

Gives explicit routing rules: use transfer_preflight for next nonce with balance and gas checks, use get_block_number for chain head. Also narrows chain scope to Ethereum/Base/Robinhood only, so when-not-to-use is covered.

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