Critical gaps across all dimensions. Tool definitions are inferred from CLI command registration (deploy-server.ts) rather than explicitly visible in MCP server code. No input schemas, parameter descriptions, or output schemas are visible in the provided source. Descriptions are present but generic (avg ~80 chars, below 194-char baseline). No evidence of error handling, validation, or recovery guidance. Tools lack parameter type definitions entirely. This server appears to be a wrapper around a CLI with minimal MCP-specific implementation.

• Create explicit MCP tool definitions with full JSON Schema input/output. Move from CLI-inferred tools to declarative MCP registration using mcp-sdk's tool.register() or equivalent.
• Add parameter descriptions for all tools. Example: cerefox-search should document 'query' (string, semantic search text), 'filters' (object with project_id, date_range, etc.), 'limit' (1-100, default 20), 'offset' (for pagination).
• Expand tool descriptions to 150-250 chars. Include WHEN to use (e.g., 'Use cerefox-search for semantic similarity; use cerefox-metadata-search for exact field matching'), WHAT it returns, and any prerequisites.
• Document output schemas for each tool. Example: cerefox-search should return {documents: [{id, title, project_id, metadata, score}], total_count, next_offset}.
• Add error handling guidance. For cerefox-ingest, document what happens on invalid documents, quota limits, and how to retry. For cerefox-search, explain empty results and suggest fallback strategies.