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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the shape of the returned telemetry (height, sync progress, peers, mempool count, version), which is valuable given there is no output schema, but it says nothing about freshness/latency characteristics, rate limits, or that the call is a side-effect-free read.

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?

Three compact clauses: what it returns, when to use it, when not to use it and what to use instead. Front-loaded with the resource, zero filler, every sentence earns its place.

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?

For a single-enum read-only status tool with no output schema, the description supplies the missing return-field context and clean routing to alternatives. Its one gap is not clarifying how it relates to the per-chain eth_node_status and xmr_node_status tools that appear to overlap in scope.

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?

Only one parameter and the schema covers it at 100%, including the btc/eth/xmr/zec enum with its own description. The description adds no syntax or constraint detail beyond the schema, so the baseline 3 for fully-covered parameters 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 gives a precise verb+resource ('run-time status of one chain's node') and enumerates the returned signals (block height, sync progress, peers, mempool tx count, client version), making the purpose concrete. It differentiates against btc_fee_estimates, btc_address_summary and xmr_pool_status, but never mentions the overlapping eth_node_status and xmr_node_status siblings, which is the most likely source of mis-selection.

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?

Explicit 'When to use' (checking whether a chain's node is synced, healthy or lagging) and explicit 'Do not use' exclusions that route the agent to named alternatives for fees, address balance and Monero pool detail. Nothing about the selection decision is left to inference.

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