Scored across 15 tools
Each tool targets a distinct retrieval or analysis mode (search vs. map vs. API lookup vs. examples vs. pitfalls vs. recipes), so boundaries are mostly clear. The main overlap is get_implementation_context, which is an orchestrator that subsumes search_docs, find_api, find_example, find_pitfall, and find_recipe, but its explicit 'high-level orchestrator' labeling mitigates confusion.
All 15 tools follow a consistent snake_case verb_noun pattern (list_sources, search_docs, get_doc, find_api, check_api, diff_docs, analyze_impact, export_agent_context, ingest_doc). The verb variety (get/find/check/diff/analyze) is intentional and readable, not chaotic.
At 15 tools, the set is well within a healthy range and each tool maps to a distinct capability in the documentation-intelligence workflow. No obvious filler or redundant tools inflate the count.
The surface covers the full lifecycle: ingest/index (ingest_doc), discovery (list_sources, get_documentation_map), retrieval (search_docs, get_doc, find_api, find_example, find_pitfall), synthesis (find_recipe, get_implementation_context), verification (check_api), change tracking (diff_docs, analyze_impact), and export (export_agent_context). Version resolution (get_version) rounds out dependency-aware workflows, leaving no obvious dead ends.