Server has 9 tools with mixed quality. Naming is inconsistent (strata_* prefix for ops, but commit_memory, recall_context lack verb clarity). Descriptions exist but are verbose, mixing Chinese and English, and lack LLM-optimized structure. Schemas are present but incomplete: many parameters lack type definitions (e.g., strata_init.mode is enum but others are underspecified). Critical issue: descriptions exceed 1024 chars and contain operational warnings that should be in error handling, not descriptions. No output schemas documented. Error handling is minimal, no recovery guidance or categorization.

• Rewrite all descriptions in English, single-language, 50 - 150 chars. Format: '[Verb] [object] [when to use]. Returns [structure].' E.g., 'Initialize memory palace with config and vector index. Call once at setup. Returns success status.'
• Rename tools with clear action verbs: strata_init → initialize_memory, strata_doctor → diagnose_memory, strata_rebuild_index → rebuild_vector_index, strata_stats → get_memory_stats, strata_project → export_memory_projection.
• Document output schemas for all tools. E.g., recall_context returns {memories: [{id, type, fact, confidence, timestamp}], total_count, next_cursor}. Include field types and descriptions.
• Add error handling to tool responses: categorize errors as retryable/user-fixable/fatal, include the invalid value and constraint violated, and suggest next steps. E.g., 'API key missing (status=EMPTY). Set STRATA_API_KEY env var and retry.'
• Move operational warnings ('禁忌') from descriptions into tool implementation. Return them as error messages when preconditions are violated (e.g., 'Cannot rebuild index while indexing service is down. Wait 30s and retry.').