Scored across 14 tools
Each tool targets a distinct action+state, and the descriptions explicitly cross-reference the confusing neighbors (e.g. bernstein_run vs bernstein_run_status vs bernstein_status; bernstein_cancel vs bernstein_shutdown_orchestrator; bernstein_complete vs bernstein_approve gated by task status). Genuinely ambiguous pairs are pre-empted in the text, so an agent can reliably select. The only overlap is status-read surfaces (run_status, status, task_capsule), and those are separated by what they read.
Most tools use a bernstein_ prefix with a verb or verb_noun form (create_task, post_message, post_artifact, cancel, claim, approve, complete), which is predictable. Deviations exist: bernstein_task_capsule is noun-only, load_skill drops the server prefix, and bare verbs sit beside verb_noun forms. Still readable and largely systematic.
14 tools for an orchestration server that must cover run lifecycle, task lifecycle, messaging, and artifacts is well-scoped. No tool looks redundant enough to be dropped, and nothing essential is obviously missing from the count.
The surface covers the main lifecycle: queue a run, create/claim/complete/approve/cancel tasks, post messages and artifacts, poll status, shut down, and inspect capsules. Gaps remain around reading existing mailbox messages (post_message and subscribe exist but no explicit mailbox fetch) and releasing/reassigning a claimed task. These are workable but could force agent workarounds.