Scored across 47 tools
Most tools are clearly differentiated with detailed descriptions; memory_search vs memory_list are explicitly framed as complements and session_context auto-invokes memory_delta, noting the redundancy. The main ambiguity risk is the large cluster of DEPRECATED message_* and task_* tools that coexist with harness-owned equivalents, which could cause an agent to pick a discouraged path, though all are clearly flagged.
Naming is highly consistent: snake_case throughout, with a predictable verb_noun pattern (memory_write, task_claim, feed_subscribe, decision_list, project_join, blueprint_instantiate, graph_link, compile_setup). Even the exception pairs like session_context/session_handoff and message_mark_read follow the same convention. No camelCase or mixed verb styles appear.
47 tools is well into the 'too many' range and near the extreme end. While the server covers a genuinely broad domain (memory, tasks, projects, feeds, decisions, blueprints, events, compile mode), the surface is padded by a large deprecated cluster of message_* and task_* tools plus several overlapping memory/retrieval operations that could be consolidated.
The domain is comprehensively covered: memory has full CRUD plus search/list/delta, tasks have a complete lifecycle with dependencies, and projects, decisions, feeds, and blueprints each have create/read/delete coverage. Minor gaps exist (graph operations are limited to neighbor/link with no delete, and there is no non-deprecated messaging path), but agents can accomplish all core workflows without dead ends.