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

Annotations cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint), so the description's burden is lower. It adds meaningful behavioral context beyond annotations: it enumerates the exact metric families (propagation delay percentiles, 90% reach time, slow miner detection, stale blocks over 2,000 heights, reorg counts and depth) that will be returned, which is more informative than a generic 'status' label.

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 single run-on sentence is long and crams many metric families together without clear front-loading of the core purpose. It is information-dense but poorly structured, forcing careful reading rather than giving a scannable summary first.

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 parameters, no output schema, and rich annotations, the description carries the burden of describing what data is returned. It does this comprehensively, naming nearly every metric family (propagation delays, percentiles, slow miners, band delays, stale blocks, reorgs, chain splits). A minor gap is that it does not describe response shape or time-window boundaries for all metrics, but overall completeness is strong.

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?

There are zero parameters and 100% schema description coverage, so the baseline is 4. The description correctly does not fabricate parameter semantics; instead it details the data categories exposed, which is the value it can add with no inputs. It could be tightened but is appropriate.

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 description names a specific subject: propagation delay statistics (median, p90, p99), 90% node reach time, slow miners, stale blocks, and reorganizations with depth/history. This is differentiated from related siblings like network_health, network_nodes, and network_trends by focusing precisely on block-propagation latency and chain-tip stability metrics. An agent can distinguish it from every listed sibling.

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 parenthetical 'from the status page' implies the source but does not state when to prefer this over siblings like network_health or network_trends. No exclusions or alternative routing are given, so usage is only implied rather than explicit.

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