Search MCP has 10 tools with significant definition quality gaps. While tool names follow the verb_noun pattern well (create_index, search_code, delete_index), most lack complete input/output schemas in the visible source code. Descriptions are present but often generic and under 100 characters. No explicit input schemas, parameter type definitions, or output schema documentation were found in the provided source excerpts. The toolDescriptions.ts file shows only standard descriptions (34-179 chars) without parameter annotations or examples of schema registration. Tool descriptions are adequate but not optimized for LLM decision-making. Parameter handling and validation rules are not visible in the provided code. Error handling guidance is missing from descriptions. No evidence of idempotent operation declarations or permission gating for destructive tools (delete_index, reindex_project).

• Add complete JSON Schema definitions for every tool input with explicit type declarations (string, number, array, object) and per-parameter descriptions. Minimum: {"type": "object", "properties": {"param_name": {"type": "string", "description": "..."}}, "required": []}
• Document output schemas in tool descriptions or a separate schema file. Specify what fields are returned, their types, and which IDs/references are needed for chaining downstream tool calls.
• Add parameter descriptions that state allowed values as enums, not examples. For search tools: 'query (string, 1-500 characters; supports regex patterns: *, ?, [a-z])'
• Expand descriptions for search tools to 100-150 chars with decision guidance: 'search_code: Find implementations, functions, patterns in code. search_docs: Find documentation, guides, architecture. search_by_path: Find files by name/glob when you know the path.'
• Implement confirmation or dry-run pattern for delete_index (e.g., require user confirmation via MRTR input_required result before destructive action).
• Add error handling guidance to tool descriptions: 'If search returns 0 results, try a broader query or check get_index_status to verify the index is populated.'
• Document pagination parameters: limit (default 20, max 100), offset/cursor, and total count in responses for all list-returning tools (search_code, search_docs, search_by_path).
• Add 'prerequisites' notes: 'search_code requires create_index to have been called first. Call get_index_status to verify.'

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

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