Ghost demonstrates solid definition quality with 17 well-named tools covering memory management, task tracking, and decision recording. Tool names follow verb_noun conventions (save, search, update, delete, pin, unpin, create, list, record, resolve, health). All tools have descriptions (10-250 chars, within 10-1024 range). Input schemas are present for all tools with typed parameters. However, there are notable gaps: output schemas are NOT documented anywhere in the source code provided, parameter descriptions could be more actionable, and some descriptions lack 'WHEN to use' context. Error handling guidance is missing from descriptions. The server supports resources and prompts (secondary to tools), suggesting mature design, but lacks tool annotations (readOnlyHint/destructiveHint) which would clarify operation semantics. Overall, this is a good server with strong naming and parameter typing, but lacks the output schema documentation and error guidance that A-grade servers provide.

• Document output schemas for all tools. Add a schema block showing: ghost_memory_search returns {memories: [{id, content, category, importance, tags, created_at}], total_count}, ghost_task_list returns {tasks: [{id, title, details, completed, created_at}], total}, etc. This is critical for agent planning.
• Add tool annotations: mark destructiveHint=true on ghost_memory_delete, ghost_task_close, ghost_memory_update (when content changes). Mark readOnlyHint=true on ghost_memory_search, ghost_search_all, ghost_project_context, ghost_task_list, ghost_decision_list, ghost_health. This prevents accidental data loss.
• Enhance parameter descriptions with examples and constraints. E.g., 'importance' should clarify: '0 = ignore in summaries, 1 = always highlight. Defaults to 0.5 (neutral). Used to rank memories in ghost_project_context.'
• Add error recovery guidance to descriptions. E.g., ghost_memory_search: 'Returns empty list if project not found or no matches. If you need to create a new project, use ghost_project_context first to verify it exists, or call ghost_memory_save to initialize.' This guides LLMs on failure modes.
• Implement confirmation for destructive operations. Add an optional 'confirm' boolean parameter to ghost_memory_delete and ghost_task_close. When false (default), return a confirmation prompt; when true, execute. Prevents accidental deletion.
• Clarify pin/unpin semantics in descriptions. E.g., 'Pin a memory to ensure it appears in ghost_project_context summaries even if low importance. Pinned memories are displayed first, then by importance. Max 5 pinned per project.'