Hivemind has 11 tools but lacks visible input schemas and descriptions in the provided source. The code shows tool files exist (setup.ts, register.ts, etc.) but no explicit tool registration with JSON Schema is visible. Tool names are reasonably verb-based (setup, register, emitEvent, query, status, reset, claimTask, startTask, completeTask, events, worktreeCleanup) but without access to the actual tool definitions in src/mcp/core.ts or tool registration code, schemas and parameter descriptions cannot be verified. Since no schemas or descriptions are shown in the provided code sample, most tools score 0 on schema and description dimensions.

• Add explicit tool registration in src/mcp/core.ts with full JSON Schema for each tool. Include inputSchema with type, properties, required array, and descriptions for every parameter.
• Write 50 - 200 character descriptions for each tool explaining WHAT it does, WHEN to use it, and any prerequisites. Example: 'Register a new agent session with the coordinator. Call this first when a Claude instance joins the hivemind.'
• Add parameter descriptions for all inputs. For 'query' tool, describe what query syntax is accepted. For 'claimTask', describe task_id format and what 'claiming' means.
• Document output schemas. For 'status' tool, specify returned fields (agent_id, status, last_heartbeat, etc.). For 'events', specify event structure and pagination.
• Implement error handling with recovery guidance. E.g., if reset fails due to active tasks, return 'Cannot reset: 3 tasks in progress. Call completeTask() first.' instead of a bare error.

Inferred effective spec: <=2025-11-25.

• Relies on Stateful initialize / Mcp-Session-Id (removed; protocol is stateless) - make each request self-contained