Scored across 23 tools
Most tools map to distinct pipeline stages or artifacts, and descriptions clearly separate near neighbors like frames vs stills and validate_storyboard vs lint_storyboard. A couple of pairs (record/probe/render, frames/stills) require careful reading, but there is no real functional overlap.
All names are lowercase snake_case, but conventions are mixed: bare verbs (record, probe), output-noun names (frames, stills, gif), get_ prefixes, and job_list/job_status/job_cancel which are not uniformly verb-first. The set is readable but lacks a single consistent verb_noun pattern.
With 23 tools, this sits in the heavy range for an MCP surface even though the demo-pipeline domain is complex. Each tool has a distinct purpose, but the count feels borderline and some consolidation could make it tighter.
The surface covers the full authoring lifecycle: scaffolding, schema/guide, validation/linting, inspection, probe/record, all render stages, stills/frames/gif/walkthrough exports, job management, environment checks, and feedback. There are no obvious dead ends or missing core operations for the stated purpose.