Scored across 7 tools
Each tool has a distinct output role—full guard run, actionable subset, explanation, report, score, evidence verification, and claim extraction. The only potential confusion is docguard_guard vs docguard_diagnose, but their descriptions clearly separate full JSON from fix-oriented results.
All tools share the docguard_ prefix and use clear action verbs, but the pattern is not fully uniform: some are bare verbs (diagnose, explain, report, score, guard) while others use verb_noun (verify_evidence, verify_claims). docguard_guard is also slightly redundant, though the set remains predictable and readable.
Seven tools is well-scoped for a documentation-compliance utility; each tool addresses a distinct stage of the guard/report/verify workflow. No tool feels redundant, and the count is neither thin nor bloated.
The set covers the full read-only lifecycle: running validators, prioritizing fixes, explaining codes, scoring, reporting, and verifying both evidence files and semantic claims. Minor gaps like a validator-listing or configuration tool are possible, but agents can work around them using the guard output and explain tool.