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

Annotations already cover readOnly, idempotent, non-destructive and openWorld, so the bar is lower. The description adds genuine behavioral context beyond them: it names the underlying node call (eth_getTotalSupply), states that the value is independently recomputed and that a 'mismatch' flag is set if the two disagree, and notes block rewards are spendable only 100 blocks later.

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?

It is a single dense paragraph of ~150 words that opens with emission-schedule exposition (halving cadence, 'no premine, burn or protocol lock') rather than the tool's behavior. Those chain facts help interpret the numbers but many sentences do not earn their place for the purpose of selecting and invoking the tool, and the useful return-value list is buried mid-paragraph.

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?

With no output schema, the description carries the burden of describing return values and does so thoroughly — head height, issued supply in wei and LAX, node vs. recomputed, share of cap, remaining to mine, reward/era, daily issuance, and next-halving fields. For a zero-parameter read tool with rich annotations, this is close to complete, missing only sibling guidance.

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?

The tool takes no parameters, so the baseline of 4 applies. The description does not need to explain inputs, and the schema is empty by design.

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?

The core purpose is stated explicitly: it 'Returns the head height, issued supply in wei and LAX from the node ... and as recomputed here from the schedule,' which is a specific verb plus resource an agent can act on. However, the description is front-loaded with chain tokenomics ('LAX issuance against the 21,000,000 cap', halving schedule) before the tool's function appears, and it never distinguishes itself from the sibling block_reward despite overlapping on 'the current reward and era.'

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?

There is no statement of when to call this versus alternatives, and no prerequisites or exclusions. Sibling tools like block_reward, mining_stats and explorer_charts plausibly overlap on supply/reward data, so an agent gets no routing help at all.

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