Scored across 59 tools
Many tools analyze alarm/health data with overlapping inputs (e.g., alarm_bad_actors, alarm_flood_analysis, alarm_cascade, alarm_rationalization_worksheet; health_summary, tag_health, historian_health, data_quality_scorecard). Deprecated tools like health_summary and anomaly_scan redirect to non-existent replacements, increasing ambiguity. While many tools are distinct, the boundaries between several analytics tools are unclear.
Tool names are predominantly snake_case with a consistent verb_noun pattern (diagnose_dataflow, monitor_changes, oee_compute, compliance_report). Protocol-specific prefixes (iec61850_, iec104_, dnp3_) and domain prefixes (plc_program_, compliance_) are used consistently. Minor deviations like protocols_supported, health_summary, and rca_corpus_from_maintenance do not break the overall pattern.
59 tools is well above the 25+ threshold for 'too many'. While the domain is broad (multiple industrial protocols, analytics, compliance, PLC analysis), the count is excessive and many tools are deprecated or overlapping. A more focused set of 15-20 tools would be more coherent.
The set covers a wide range of operations: protocol reads, diagnostics, analytics, compliance, historian, fleet, PLC program analysis. However, several tools reference missing components (e.g., opcua_discover_tags, modbus_apply_template, opcua_health_summary) and deprecated tools point to non-existent replacements, creating dead ends. Core workflows exist but gaps in referenced helpers prevent full coverage.