Scored across 15 tools
Most tools target clearly distinct resources (suites, artifacts, variables, chat, dispatches). However, three read tools — wopee_fetch_test_inventory, wopee_fetch_recent_executions, and wopee_fetch_executed_test_cases — all report test execution status with overlapping scope, and only the descriptions' explicit 'prefer X over Y' guidance keeps them apart.
Every tool follows the same wopee_<verb>_<noun> snake_case pattern (fetch_, create_, update_, generate_, dispatch_, send_, read_). The single use of 'read' instead of 'fetch' for chat history is trivial and does not break the predictable convention.
15 tools is well within a sensible range and each one maps to a distinct capability (suite lifecycle, artifact lifecycle, agent/analysis dispatch, variables, chat, GitHub issues). No tool feels redundant or bolted on.
Coverage is strong: suite creation (blank + auto-analyze), artifact generate/fetch/update, variable read/upsert, chat read/send, status retrieval, and issue reporting. Minor gaps exist — no suite/artifact deletion or renaming, and GitHub issue creation has no read/update counterpart — but core workflows are fully supported.