Scored across 30 tools
Most tools target clearly distinct resource+action pairs, and descriptions explicitly delineate entry types (summary, verdict, question, answer, resolution, generic entry). A couple of near-overlaps exist: transition (status change) vs move_task (project move), and add_entry vs add_project_entry share the same action on different scopes, which could cause occasional misselection.
The dominant pattern is consistent snake_case verb_noun (read_project_entries, create_task, update_task, close_task, add_verdict, etc.). A handful of tools break it with bare verbs (link, unlink, ask, answer, resolve, transition), and the get_/read_ prefix usage is not perfectly uniform, but everything remains readable and lowercase.
30 tools is above the comfortable range and feels heavy, but the domain is genuinely broad (projects, tasks, entries, links, participants, attributes, journal). Each tool maps to a distinct operation, yet the surface could likely be consolidated (e.g. entry-creation variants).
Full lifecycle coverage: project create/update/archive/restore/list/get, task create/update/move/transition/close/get/search, entry add/read, links link/unlink, participant register/update/list, attributes set/remove, and a journal stream. Entries are intentionally immutable and projects archived rather than deleted, so no obvious dead ends.