Scored across 17 tools
Each tool targets a distinct resource and action, with cross-references clarifying when to use similar tools like configure_device vs configure_reporting vs interview_device. The read-only tools (list_devices, get_device, health_report, network_map) have clearly differentiated scopes.
All tools share the z2m_ prefix and use clear descriptive names, but a few read-only tools (z2m_bridge_info, z2m_health_report, z2m_network_map) use noun phrases rather than the verb_noun pattern seen in most other tools (list, get, set, rename, configure). This is a minor deviation from an otherwise predictable convention.
At 17 tools, the set is slightly above the typical 3-15 range, but the Zigbee domain is complex and each tool covers a genuinely distinct operation. No tool feels redundant, and the count is justified by the breadth of device, group, binding, and network management tasks.
The tool set covers the major lifecycle operations: pairing via permit_join, listing and inspecting devices, changing state and options, configuring reporting, managing groups and bindings, OTA updates, health checks, and logs. The most notable gap is the lack of a device removal/delete tool, and there is no bridge restart or firmware update tool, but these are minor for typical automation scenarios.
