Most tools target distinct operations: whole-project vs single-file analysis, severity vs category filtering, and the custom-rule lifecycle (add/remove/list/execute/validate) are clearly separated. The main overlap is check_dependencies vs get_vulnerability_report, whose description ('offline dependency report listing all project dependencies') suggests it largely duplicates dependency analysis rather than delivering the CVE lookups its name implies.

Every tool follows a consistent snake_case verb_noun pattern (analyze_project, get_sqale_metrics, list_custom_rules, add_custom_rule, validate_custom_pattern). Verb choices (analyze/get/list/add/remove/execute/check/validate) are conventional and predictable for their actions.

16 tools is slightly above the comfortable band but justified by the breadth of the domain (analysis, metrics, issue filtering, recommendations, custom rules, dependencies, config). Each tool maps to a real user need rather than being redundant filler.

The surface covers the core lifecycle: analysis (project/file), summary and SQALE metrics, filtered issue retrieval, recommendations, full custom-rule management, dependency checking, and config validation. The one notable gap is that vulnerability reporting stops at an offline dependency listing with no actual CVE data, leaving a dead end for security review.