Agent-relay defines 6 tools with basic schemas and descriptions, but falls short of production quality. Tool names lack clear verb prefixes (poll, claim, heartbeat, escalate, deliver, create are acceptable but generic). Descriptions are present but brief (10-80 chars), below the 50-200 char LLM-optimized baseline. Parameter descriptions are sparse or missing entirely, most params lack type hints or constraints. Output schemas are not documented. Error handling is minimal. The 'create' tool definition is split across files (src/mcp/tools.ts vs scripts/mcp-server.mjs), making verification incomplete. No evidence of pagination, idempotency hints, or recovery guidance.

• Add 50-200 character descriptions to all tools. Example: 'claim' → 'Atomically claim a mission and transition it to Running state. Call after poll() to reserve a task. Returns mission_id and status. Fails if already claimed by another agent.'
• Document every parameter with type, format, and constraints. Example: 'column: string enum (ready|inbox|running|review|done), defaults to ready. Filters which board column to list missions from.'
• Define output schemas for each tool. Example: poll returns {missions: [{id, title, tags, priority, agent_skills_match}], total_count, next_cursor}.
• Add error handling guidance. Example: 'claim fails with 409 Conflict if mission already claimed, call poll() again to find unclaimed missions. Fails with 404 if mission_id invalid, verify mission exists before claiming.'
• Implement pagination for poll: add offset/limit params, return total_count and next_cursor, cap results at 20-50 items per call.