Scored across 26 tools
Most tools have clearly distinct resource+action targets, and descriptions explicitly redirect between similar tools (get_index vs get_outline, get_element_text vs get_page_image, search_distributors vs project_availability). Some boundaries still require careful reading: list_items vs get_page_map vs get_index, and project_status vs project_check vs project_sync could be confused at a glance.
The set is predominantly consistent snake_case with predictable verb_noun spacing and a coherent project_ prefix family. Minor deviations exist: noun-only names like part_links and distributor_status, and mixed verb families (get_/save_/find_/set_/add_/search_) that are still readable.
At 26 tools the surface exceeds the 25-tool threshold, which is heavy even for a domain this broad (document ingestion, reading, facts, project lifecycle, distributors). Several lifecycle and distributor tools could plausibly be consolidated or moved to CLI per the descriptions themselves.
Coverage is strong: document ingestion (add_document), reading (text, image, index, outline, search, page map), fact capture/verification, project add/update/remove/sync/check, and distributor availability/ordering. Minor gaps remain: no tool to delete a document from the central store, no fact deletion, and no direct CAD file download (delegated to part_links and external tools).