Slowave provides 5 memory-management tools with comprehensive input schemas and clear descriptions. All tools are properly named with action verbs (slowave_activate, slowave_remember, slowave_recall, slowave_feedback, slowave_commit). Input schemas are fully defined with types, enums, descriptions, and validation constraints. However, output schemas are not documented in the source code provided, and descriptions, while present, are quite terse (20-60 characters), well below the baseline of 194 characters for production tools. Error handling and recovery guidance are not visible. Tool composition is sound: each tool has a single responsibility within the memory management lifecycle. The server correctly implements batch operations (slowave_remember and slowave_feedback accept array parameters for batch upsert), reducing sequential call overhead.

• Expand tool descriptions to 100 - 200 characters. Add WHEN guidance: 'slowave_activate: Call first to open a new task session. Use when starting a fresh problem-solving context or switching to a new goal. Returns session_id needed for all subsequent memory operations.'
• Document all output schemas. For each tool, specify the response structure: e.g., slowave_recall returns {session_id: string, memories: [{type: string, content: string, relevance: number, occurred_at: string}], next_cursor?: string}.
• Add error handling guidance to descriptions. E.g., 'slowave_recall: Returns empty memories if query matches nothing. If you need to recall specific items, try broader queries or use slowave_remember to capture the missing information first.'
• For enum parameters, add per-value descriptions. E.g., for slowave_remember type: 'fact: unchanging information (e.g., "Paris is the capital of France"); preference: user/agent preference (e.g., "prefers markdown over HTML"); decision: a choice made (e.g., "chose library A over B"); constraint: a limitation (e.g., "max 3 API calls per minute"); instruction: a directive (e.g., "always use v2 API"); lesson: learned insight (e.g., "retry with exponential backoff"); warning: risk alert (e.g., "deprecated endpoint"); open_question: unresolved item (e.g., "how to handle timezone edge cases?"); task: a subtask (e.g., "fetch user profile"); artifact: reusable code/config (e.g., curl command).'
• Document mutually exclusive parameters explicitly. E.g., slowave_feedback: 'Either supply retrieval_id (single feedback) OR items array (batch feedback), not both. If providing retrieval_id, include memory_feedback or procedure_feedback or both.'

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

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry