Scored across 6 tools
Each tool targets a distinct diagnostic axis (consensus round, node sync, peers, validator signing, upgrades), and descriptions include explicit cross-references such as 'does NOT check peers (use peer_health)'. The only real overlap is fleet_overview, which aggregates the same signals as the four single-purpose tools, but the 'sweep first, then drill in' framing makes the boundary workable.
All six names follow the same noun_noun convention (resource + aspect of health: node_status, peer_health, validator_health, upgrade_readiness, consensus_diagnosis, fleet_overview). No mixing of verb styles, casing, or languages.
Six tools is tightly scoped for a CometBFT diagnostics server: one aggregate sweep plus five focused probes covering consensus, sync, p2p, signing, and upgrades. Every tool maps to a distinct failure mode an operator would investigate.
The diagnostic surface covers the main halt/liveness causes (quorum, sync, isolation, jailing, upgrade) plus a fleet-wide aggregate, which is strong for a read-only diagnosis domain. Minor gaps: no mempool/tx-layer inspection and no historical or trend view of past incidents, though these are arguably out of scope.