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

Adds substantial context beyond the annotations: malformed addresses are rejected with 400 and uncharged, pricing is $0.01/call with 25 free calls, failed calls are free, and repeats are not free. That last point usefully explains the economic consequence behind idempotentHint=false. It stops short of describing the response shape or chain-reorg handling, which keeps it from 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?

Front-loads the core definition, then usage, then error and pricing semantics, with no filler sentences. Pricing and the 'repeats are not free' clause overlap slightly, and the error/payment details crowd a simple one-parameter read tool, but every sentence carries information.

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 description covers what it returns (confirmed and pending counts), what breaks it (400 on malformed address), cost model, and safe-read semantics. An agent has everything needed to call it correctly and interpret pricing.

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?

With a single parameter at 100% schema coverage, the baseline is 3; the description exceeds it by giving a concrete example address and stating the validation failure mode for a malformed one, which the schema's bare '0x address' does not convey.

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)') scoped to a named chain (Mantle) and a named address type (0x), and adds the confirmed-plus-pending detail that distinguishes it from a naive nonce lookup. Chain-specific siblings (eth_nonce, base_nonce, etc.) are already separated by name, and the description makes the Mantle scope unambiguous.

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 when-to-use cases ('build the next transaction', 'tell whether an address has ever sent anything') and explicitly routes the balance case to mantle_balance instead. Nothing about tool selection is left to inference.

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