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

The description says 'Read-shaped tools only (anything that buys, sells or writes refuses),' which strongly implies a read-only tool, while the annotations declare readOnlyHint: false. This is an annotation contradiction. The description also adds unrelated platform prose instead of clarifying behavior.

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?

The core purpose is front-loaded, but the description then drifts into unrelated boilerplate about the server, 'a live seat on The Wall,' and a listing URL. It also contains a truncated, confusing phrase: 'with the correct chain i —'. Several sentences do not earn their place for a tool-specific definition.

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 should explain what the tool returns or how the result is presented, but it does not. It also does not clarify how the target chain is selected given there are no parameters. The liveness motivation is explained, but the operational context an agent needs is incomplete.

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 has zero parameters and 100% schema description coverage, so the schema carries no burden. With 0 params, the baseline is 4, and there is nothing meaningful for the description to add about parameters.

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 opening sentence states a specific verb, resource, and conceptual distinction: 'Check that a chain is actually producing blocks, rather than merely answering.' This makes the tool's purpose unambiguous and distinguishes it from generic chain-query tools that might just return data from a halted chain.

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?

The description implies when to use it — when you need proof of block production, not just a response — but it never names alternatives or explicitly states when not to use it. The liveness rationale is helpful, but usage guidance is left mostly to inference.

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