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

Annotations already declare readOnly/destructive/openWorld, so the safety profile is covered. The description adds substantial behavioral context beyond them: the nonce is bound to (chainId, contract, minter) and worthless to other addresses, the grind is deadline-bounded by a server-enforced 8s cap, and the best valid nonce is returned even on timeout.

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 imperative and the core action, then binding constraint, then the deadline caveat. Dense but nearly every sentence earns its place; the 'DO THE WORK' opener is slightly theatrical but functions as emphasis.

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?

No output schema exists, yet the description enumerates the return fields (nonce, work hash, leading-zero-bit difficulty, band) and the partial-result behavior. Combining that with the binding and timeout context, an agent has everything needed to call this 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 coverage is 100%, so the baseline is 3, but the description reinforces the critical semantic that minter must be the transaction sender (the proof is bound to it) and gives difficulty guidance that explains why targetBits above ~20 will time out on this server. That adds meaning beyond the schema field text.

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 ('Grinds keccak256 to find a proof-of-work nonce valid for a specific minter address') and its role among siblings: it is the mining operation, distinct from nonce_verify, nonce_census, and nonce_mint_packet. An agent can tell immediately what it produces.

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?

Explicitly says when to use it ('the only way to become eligible to mint an 8004 NONCE piece'), when not to use it ('for difficulty above ~20 bits, run the local miner script instead'), and warns to mine for the address that will actually send the transaction. Alternatives are named with the condition that selects them.

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