Ingat exposes 5 tools with basic descriptions but critical gaps in schema completeness and parameter documentation. Three tools (health, listProjects, fetchRecent) lack visible input schemas entirely. searchContexts and saveContext have partial schemas but missing parameter descriptions. No tool includes output schema documentation. Naming is reasonable (verb-noun pattern) but descriptions are generic and lack LLM-optimization guidance. No error handling patterns, no idempotency hints, no permission gates documented.

• Add complete JSON Schema input definitions for all tools. health and listProjects should declare empty input objects if they take no parameters. fetchRecent should formalize the 'limit' parameter with type, min, max, and description.
• Document output schemas for all tools. E.g., health should return {status: string, uptime_ms: number, components: {database: string, embeddings: string}}. searchContexts should return {results: [{id, title, score, project}], total_count: number}.
• Expand descriptions to 80 - 150 chars with WHEN and WHY. E.g., 'Check if the Ingat service is running and all components (database, embedding engine) are healthy. Call this before other operations to verify connectivity.'
• Add parameter descriptions for all inputs. searchContexts 'filters' should document valid keys (e.g., 'project, tags, date_range'). saveContext 'tags' should clarify format (e.g., 'array of lowercase strings, max 5 tags, 1-20 chars each').
• Add error recovery hints in descriptions. E.g., saveContext: 'If project not found, call listProjects() to see available projects.' searchContexts: 'Returns empty results if no matches; try broader search terms or check filters.'

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry