Scored across 23 tools
Each tool targets a distinct resource and action, and the descriptions actively cross-reference each other (e.g. get_check vs diagnose_check vs list_results; list_incidents vs manage_status_page_incident for internal vs customer-facing incidents). The few superficially similar pairs are explicitly delineated, leaving little room for misselection.
Nearly all tools follow a predictable verb_noun pattern (list_checks, get_check, create_check, update_check, delete_check, get_status_page, etc.). Minor deviations exist: the bare verb 'probe' breaks the pattern, and the manage_status_page_* tools use a 'manage' verb instead of the create/update/delete convention used elsewhere.
At 23 tools the surface sits on the heavier end, but the domain genuinely spans several resource families (checks, results, incidents, status pages, sections, resources, publications), so most tools earn their place. A few consolidation candidates (e.g. the three manage_status_page_* tools) keep it just short of ideal.
Checks have full CRUD plus validate/run/diagnose, status pages and their sub-resources have full lifecycle coverage, and results/incidents/regions/types are sensibly read-only. Minor gaps exist (check groups are list-only, and internal incident state changes aren't exposed), but these are largely consistent with the domain's generated/read-mostly nature.
