Most tools are separable (list_jobs vs get_job vs queue_summary vs cancel_job), but submit_job and submit_job_json are explicitly described as completely equivalent entry points, which forces an arbitrary choice. The three discovery tools (capabilities, action_schema, studio_catalog) also overlap in intent and rely on prose to be told apart.

Consistent snake_case throughout, but conventions are mixed: verb_noun (list_jobs, submit_job, get_job, cancel_job) alongside bare noun phrases (capabilities, action_schema, studio_catalog, artifact_manifest, queue_summary). Still readable, but the pattern does not predict whether a tool is an action or a resource view.

Ten tools is a well-scoped size for a job submission/inspection server. The only redundancy is submit_job_json duplicating submit_job, which costs one slot but is documented as a convenience.

The lifecycle is largely covered: discovery (capabilities, action_schema, studio_catalog), submit, poll (get_job, list_jobs, queue_summary), cancel, and artifact export. Gaps are minor and arguably deliberate — no retry/resubmit tool and no job deletion or bulk cleanup.