Scored across 12 tools
Most tools target clearly distinct operations (score, guard, explain, report, read_section). However, docguard_guard, docguard_diagnose, and docguard_report all revolve around running validators and reporting results, and docguard_anchors overlaps with docguard_docs_for_path on doc-to-code link discovery, creating mild confusion. Descriptions do clarify the boundaries reasonably well.
All tools share a consistent docguard_ prefix, which aids grouping. The suffixes mix bare nouns (score, anchors, guard, report, diagnose) with verb_noun forms (verify_evidence, docs_for_path, read_section), a minor inconsistency that is still readable and predictable.
12 tools is well within the appropriate range for a documentation-governance server and each covers a recognizable facet. There is slight redundancy among guard/diagnose/report, which keeps it just short of ideal scoping.
The surface covers the full analysis lifecycle: scoring, validation, finding explanation, evidence and claim verification, compliance reporting, doc structure, section reading, and task context. Gaps are minor, e.g. no explicit suppression or configuration management tools, but the core domain is well covered.