Memory Engine provides 8 tools with reasonably detailed descriptions and structured input schemas. Most tools have descriptions (100%) and parameter documentation is generally present, but there are several gaps that prevent a higher score: (1) Output schemas are not documented for any tool, the rubric requires this for A-grade work; (2) Error handling guidance is absent, tools do not indicate what to do on failure, retryability, or recovery steps; (3) Some parameter descriptions lack constraints (e.g., days accepts 0 for 'all time' but this boundary is implicit, not explicit); (4) Tool composition could be improved, memory_search and memory_search_knowledge are very similar and risk LLM confusion; (5) The memory_save tool accepts a 'review_trigger' parameter described only as 'When to re-evaluate this knowledge', no valid values or format are specified. Per-tool scores range from 55 - 72, with search/read tools scoring higher (clearer intent) and write tools lower (missing error context).

• Document output schema for all 8 tools. Specify all returned fields, their types, and whether they are always present. Example for memory_search: {entries: [{id: int, content: string, role: string, timestamp: string, score: float}], total_count: int, next_cursor?: string}
• Add error handling guidance to each tool description. Pattern: 'Returns: [...]. On failure: [retry guidance or user-fixable steps]. Common errors: [list with recovery hints].'
• Rename memory_search_knowledge to memory_search_curated or memory_search_kb to disambiguate from memory_search. Make the distinction obvious in tool names, not just descriptions.
• Formalize 'status' parameter in memory_search_knowledge and memory_agent_knowledge as enum: ['ACTIVE', 'STALE', 'ARCHIVED', ''] instead of text description.
• Specify valid values for memory_ingest 'source' as enum: ['all', 'latest', 'session', 'prompts']. Same for 'tool_source': ['claude_code', 'copilot', 'codex', 'all'].
• Define 'review_trigger' format in memory_save. Examples: 'ISO date (e.g., 2026-02-24)', 'duration (e.g., "7 days", "30 days")', or enum like ['never', '7d', '14d', '30d'].
• Add pagination metadata to search responses. Return {entries: [...], total_count: int, has_more: bool, offset: int, limit: int} so agents can fetch subsequent pages.
• Add recovery hints for common failures. E.g., 'If no results found: Try shorter query, remove filters, or call memory_list_projects to see what projects exist.'
• For write tools (memory_save, memory_ingest, memory_add_to_project), document idempotency and retry safety. Example: 'memory_save auto-deduplicates by (topic, agent), safe to retry. Returns: {id: int, created: bool, updated: bool}'.