Each tool has a fairly distinct purpose: docs search, config-key explanation, component checklist, metadata-type listing, and config reading. The only mild overlap is between mcdev_search_docs and mcdev_explain_config_key, since both address configuration concepts, but the search-vs-explain distinction is reasonably clear.

Four tools use a consistent mcdev_ prefix (mcdev_search_docs, mcdev_explain_config_key, etc.), but read_mcdev_project_config breaks the pattern by placing the prefix mid-name and using a different verb style. The mixed convention is still readable but not uniform.

Five tools is well-scoped for a documentation and configuration helper server. Each tool covers a distinct facet of assisting with mcdev/SFMC development without redundancy.

The surface covers the key helper workflows: searching docs, explaining config, authoring checklists, listing metadata types, and reading project config. Minor gaps exist (e.g. no config validation or write/migration helper), but the read-only assistance scope is largely covered.