Retinue provides 8 tools with complete input schemas and descriptions. Naming follows verb_noun convention (task_list, task_new, task_update). Descriptions are present and contextual (avg ~80 chars), exceeding the 20-char minimum. All parameters have type definitions and descriptions. However, output schemas are not documented in the visible code, the tool implementations return dicts but no schema is declared to the MCP client. Error handling is minimal; no recovery guidance or actionable error messages visible. The server lacks tool annotations (readOnlyHint, destructiveHint) despite clear risk classifications (READ_ONLY vs WRITE). Parameter descriptions could be more prescriptive about format/constraints (e.g., task_id format rules, priority enum values are declared but not explained in descriptions).

• Add output schema definitions to all tools. Document the structure of returned dicts (e.g., task_list returns array of {id, title, status, holder, priority, blocked_by, blocks, ready, last_receipt_at}). Use JSON Schema in the tool registration.
• Annotate tools with readOnlyHint and destructiveHint. Mark task_list, ready_work, my_tasks, task_receipt with readOnlyHint=true. Mark task_new, task_dependency_add/remove, task_update with destructiveHint=true.
• Enhance parameter descriptions with format rules and state machine constraints. E.g., 'task_id: Unique identifier (alphanumeric, no slashes or dots). Status transitions: queued→doing→done or handoff; doing may become blocked; handoff/blocked return to doing.'
• Add error recovery guidance. Catch ProtocolError and return structured errors like '{"error": "unknown task: xyz", "recovery": "Call task_list() to see available tasks."}'
• Document pagination for task_list. Add optional limit and offset parameters, return total count, and cap results at 50 items by default to prevent context window exhaustion.