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

Annotations already cover safety (readOnly, idempotent, non-destructive, open-world), so the bar is lower. The description adds genuine semantic context beyond the annotations: bands are UNCAPPED and emergent rather than designed, results are counts only, and data is read live from chain. It does not cover pagination or sampling completeness, which keeps it short of 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?

Three sentences, front-loaded with the resource and scope, then the key semantic caveat (uncapped bands) and the return contract. No filler or repetition of structured fields.

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 read-only census tool with rich annotations and no nested parameters, the description covers what the tool computes and what it returns qualitatively. With no output schema, a sentence on the shape of the counts payload would fully close the gap.

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 limit parameter is already richly documented, including the 500 cap and the eth_call/RPC rate-limit rationale. The description adds nothing about the parameter, so the baseline of 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+resource: the live distribution of minted 8004 NONCE pieces across difficulty bands, read from chain. It is clearly distinguishable from adjacent siblings like nonce_get_piece (single piece) and nonce_info (metadata). An agent can pick this over its neighbours without opening a 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?

Usage is only implied: this is the aggregate/census view, in contrast to the per-piece siblings. The clause 'Returns raw counts only — no interpretation' sketches what it is not for, but no alternative is ever named and no when/when-not condition is stated explicitly.

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