Scored across 7 tools
Each tool targets a distinct operation: listing tasks, listing templates, running, tailing output, restarting, stopping, and disposing. The descriptions reinforce the boundaries, e.g., tail's status line makes it unnecessary to call list_tasks just to check liveness.
All tools share the overseer_ prefix and follow a snake_case verb-first pattern. The two list tools include their noun (tasks/templates), while the task lifecycle operations use clear verbs (run, tail, restart, stop, dispose), which is consistent and predictable.
Seven tools is well-scoped for a task-runner server: discovery (list templates), listing (list tasks), execution (run), observation (tail), and lifecycle control (restart, stop, dispose). Every tool earns its place with no redundant overlap.
The surface covers the full task lifecycle: create/start (run), read/list (list_tasks, list_templates, tail), and delete/cleanup (dispose), plus control operations (restart, stop). The descriptions also explicitly account for short-lived commands being handled outside the server, so there are no obvious dead ends.