Verify a PoW nonce

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

With no annotations, the description carries the full burden and does disclose meaningful traits: the computation is local, the result is compared against a 'live' required difficulty (implying chain-state dependence), and no transaction is broadcast. It omits what happens on failure or whether it returns a boolean vs a bit count, but the safety/behavior profile is substantially covered.

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?

Two sentences, no filler, with the operation and its acceptance test front-loaded before the read-only caveat. Every clause 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?

There is no output schema, so the description should describe the return value; it implies a pass/fail check against difficulty but never states the actual return shape (boolean, bits, difficulty value). The missing inputs chainId and core are also unexplained, though the algorithm sentence hints they come from live state.

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 goes further by showing exactly where 'miner' and 'nonce' sit in the preimage (chainId || core || miner || nonce), giving the parameters positional meaning the schema's terse descriptions do not.

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 operation: locally computing keccak256(chainId || core || miner || nonce) and checking leadingZeroBits against live difficulty. The verb 'verify' plus the exact preimage and acceptance criterion clearly distinguishes it from the sibling find_nonce (search) without needing to open either 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?

Implies usage context ('verify a PoW nonce') and adds 'Read-only; no transaction is sent,' but never says when to pick this over find_nonce or when verification is needed (e.g., before submitting). Usage is implied rather than stated with exclusions or an alternative.

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