Critical failures across naming, descriptions, and schemas. 53 tools defined but most lack actionable descriptions and complete input schemas. Tool names are inconsistent (verb_noun vs bare nouns: 'status' vs 'search', 'wake_up' vs 'health'). Most parameter descriptions are generic ('Optional realm filter' repeated 20+ times). Input schemas for ~30 tools are empty objects {} with no parameters defined. No output schemas documented. Error handling absent. This server fails to meet baseline production standards for agent tool definition.

• Add complete input schemas to all 30 tools with empty {} schemas. Include parameter types, descriptions, and constraints (enums, min/max, patterns). Example: search_kg should accept 'query' (string), 'limit' (integer, 1-100), 'filters' (object with realm, signal, topic).
• Expand all tool descriptions to 50-200 characters. Replace generic 'Optional realm filter' with actionable context: 'Search the knowledge graph for entities matching the query. Use realm to scope to a specific domain (e.g., "engineering", "product"). Returns ranked results with relevance scores.'
• Document output schemas for all tools. Specify returned fields, types, and pagination. Example: search returns [{id, title, realm, relevance_score, created_at}], total_count, next_cursor.
• Rename ambiguous tools: 'list' → 'list_cells', 'status' → 'get_system_status', 'health' → 'check_health', 'history' → 'get_cell_history'. Ensure all names start with action verbs (get_, list_, search_, create_, update_, delete_).
• Add error handling guidance to all WRITE tools (add_cell, revise_cell, etc.). Include: what can fail, how to detect it, and what to do next. Example: 'If realm validation fails, call list_realms() to see available options.'