Critical gaps across all dimensions. Tool descriptions are present but minimal (10-50 chars, well below the 194-char baseline). Input schemas visible but lack parameter descriptions, most params have only type and name, no guidance on format, constraints, or valid values. No output schemas documented. Error handling absent. Destructive tool (delete_project) has no confirmation pattern. Parameter naming inconsistent: 'query' vs 'pattern' for search tools; 'project' appears in 9/10 tools but lacks description in most. No tool annotations (readOnlyHint, destructiveHint). Composition issues: search_graph, query_graph, and search_code overlap functionally without clear differentiation. STDIO transport caps protocol readiness at 50, further limiting production viability.

• Add 50-150 character descriptions to every parameter. Example: 'query (string): Search query in natural language or regex syntax. Supports wildcards (*) and boolean operators (AND, OR, NOT). Max 500 chars.'
• Document output schemas for all tools. Example for search_graph: 'Returns {results: [{symbol: string, file_path: string, line_number: int, context: string}], total_count: int, next_cursor?: string}'
• Consolidate search tools: merge search_graph, query_graph, and search_code into a single search_codebase tool with a 'search_type' enum parameter (symbol|pattern|text) to eliminate ambiguity.
• Add confirmation pattern to delete_project: require a 'confirm: true' parameter or implement a two-step delete (mark_for_deletion → confirm_deletion) to prevent accidental data loss.
• Annotate tools with readOnlyHint and destructiveHint. Mark index_repository with destructiveHint=true (modifies graph state); mark delete_project with destructiveHint=true and add error recovery guidance.

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

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