Dense-Mem provides 6 tools with schemas and descriptions visible in test files. Naming follows verb_noun convention consistently (list_, get_, resolve_, eval_run_, eval_list_, eval_run_). Descriptions are present but vary in depth (44-195 chars). Input schemas are well-structured with types, required fields, and enums where appropriate. However, parameter descriptions are sparse or missing in critical tools (list_dreams has no description for 'status' enum), and output schemas are not documented. The server targets a specialized domain (hypothesis memory management) with sophisticated evaluation features, but lacks guidance on error recovery and chainability between tools. Tools are functional but not optimized for LLM decision-making at the description level.

• Document the 'status' enum for list_dreams with explicit valid values: e.g. 'enum: ["active", "archived", "rejected"]' and describe each in the parameter description.
• Add output schema documentation to every tool. For list_dreams, document: '{ dreams: [ { id: string, hypothesis: string, status: string, created_at: datetime } ], total_count: integer, cursor?: string }'. Reference this in the tool description.
• Add nested parameter descriptions: in eval_run_dream_cycle.seed_dreams, document what each field (hypothesis, what_if, likelihood, confidence) means and how they influence the cycle.
• Add error handling guidance to all descriptions. E.g. 'Returns 404 if hypothesis_id not found. Consider calling list_dreams to find valid IDs. Returns 400 if decision not in [reinforce, stale, reject, confirm_true, confirm_false].'
• Document pagination explicitly: 'Returns paginated results. Use cursor from response to fetch next page; omit cursor for first page. Cursor is opaque; do not construct manually. Returns cursor=null when end-of-list reached.'
• For write tools, state idempotency clearly: 'Calling this tool twice with the same hypothesis_id and decision is idempotent, the second call returns the same result without duplicating feedback.'
• Add tool annotations (readOnlyHint, destructiveHint) if supported by the go-sdk. Mark list_dreams, get_dream, eval_list_knowledge_refs, eval_run_recall_case as readOnlyHint=true; mark resolve_dream_feedback and eval_run_dream_cycle as destructiveHint=true.