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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely non-annotated behavior: it enumerates the returned fields (chain, ok, synced, height, peers, mempool, client, state) and discloses the important edge case that a not-yet-live chain returns served=false plus a tier rather than an error, which prevents an agent from misreading a non-error response as a failure.

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?

Front-loaded with the core purpose, then organized into 'When to use', 'Do not use' and 'Returns' segments. Every clause carries information: the use-case questions, the three tool redirects, and the return-field list, with no filler or restatement of the title.

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, and the description compensates by listing the response fields exactly and explaining the served=false/tier fallback. For a single-required-enum-parameter read tool with full annotation coverage, nothing an agent needs to call and interpret it is missing.

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 schema description coverage is 100%, with the enum fully documented in the schema, so baseline is 3. The description names the chain concept but adds no meaning beyond the schema — nothing about whether the enum values behave identically, what 'served=false' means per tier, or chain-specific caveats.

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 verb+resource combination: live run-time state of one chain's node, with the concrete attributes it exposes (height, peers, mempool, client version). The 'Do not use' clause positively routes three lookalike tasks (fees, a specific payment, ZEC pool distribution) to their own tools, so an agent can separate it from btc_get_fee_rates, btc_get_transaction and zec_get_pool_status without reading any 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?

Gives explicit when-to-use questions ('is this chain's node synced, healthy or lagging') and explicit exclusions naming three alternative tools. The one real gap is that it never addresses the per-chain node-status siblings (tron_get_node_status, xmr_get_node_status) or the *_get_mempool_state tools, so an agent must still guess whether chain_status supersedes those for a single chain.

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