Server has well-structured tool definitions with complete JSON schemas and clear descriptions. All 7 tools follow verb_noun naming (events_*, system_*) and include parameter descriptions. However, output schemas are not formally documented in the code, parameter constraints lack depth (e.g., no min/max for numeric limits), and error handling is minimal. Descriptions average ~100 chars, which is adequate but could be more prescriptive about when to use each tool vs. alternatives. No tool annotations (readOnlyHint, destructiveHint) despite all tools being read-only.

• Add formal JSON Schema definitions for all tool return types. Document fields like 'events' (array of objects with timestamp, unit, message), 'count' (integer), 'anchor_at' (ISO 8601 string). Include in tool registration or separate schema file.
• Add min/max constraints to numeric parameters: limit (1 - 100), since_seconds_ago (0 - 86400), window_seconds (1 - 3600), start_seconds_ago (0 - 86400). Update parameter descriptions to include these bounds.
• Add readOnlyHint: true to all tool schemas. Update tool registration to include 'readOnlyHint' in the schema object for each tool.
• Enhance error messages with recovery guidance. E.g., 'ollama client unavailable; semantic search disabled. Try events_search() for keyword matching instead.' or 'seconds_ago must be > 0; use a positive integer representing seconds in the past.'
• Add tool selection guidance in descriptions. E.g., events_search: 'Use for keyword/substring matching. Faster than semantic search but requires exact terms.' events_semantic_search: 'Use for meaning-based search when keywords are unclear. Requires ollama embeddings service.'