Scored across 40 tools
Most tools are separated by namespace and resource type (layout, part, motion, background, narrative), which helps. However, there are near-overlaps like layout.batch_ingest vs page.batch_analyze, layout.inspect vs page.analyze, and several search tools (layout.search, design.search_by_image, design.similar_site, search.unified) that could be confused without careful reading. The deprecated search.facets adds further ambiguity.
The namespace.action pattern is broadly consistent, but the action segment mixes styles: page.getJobStatus and page.getBatchStatus use camelCase while page.batch_analyze uses snake_case, and design.track_changes/design.regression_test use compound verb phrases. The naming is readable but not predictable enough to feel fully coherent.
40 tools is well above the heavy threshold, and the set includes deprecated (search.facets), internal monitoring (embedding.quality, system.health), and narrow utilities (brief.validate, style.get_palette) that suggest scope creep. The domain is broad, but many tools could be consolidated or removed without losing core capabilities.
Core workflows are covered: URL ingestion, analysis, semantic search across components, comparison, report/code generation, and GDPR delete/export. However, there are notable gaps such as no page-level retrieval/inspection tool, no update/delete operations for design patterns or palettes, and accessibility/performance audits not integrated into page.analyze. Agents can work around these, but some workflows will hit dead ends.
