MetaSearchMCP provides 14 tools with complete input schemas and descriptions across the board. All tools follow verb_noun naming conventions (search_*, list_*, compare_*, provider_*). However, definition quality is held back by: (1) Generic, boilerplate descriptions that lack specificity about WHEN to use each tool vs. alternatives; (2) No output schema documentation, responses are not formally specified, forcing LLMs to infer result structure; (3) Minimal error handling guidance, no recovery hints or retry classification; (4) Parameter descriptions are functional but lack constraint details (e.g., what does 'tag' mean in provider_health?); (5) No documented differences between search_web, search_google, search_academic, search_code, etc., an LLM must guess which to call. Tools are well-formed but lack the LLM-optimization and composition clarity needed for a 70+ score.

• Document the output schema for every tool. Specify field names, types, and structure. Example: 'Returns {results: [{title, url, snippet, date, source}], total_count, next_cursor, partial_errors: [{provider, error_message}]}'.
• Rewrite search_* tool descriptions to clarify PURPOSE and SCOPE. Example for search_code: 'Search code repositories and package registries (GitHub, npm, PyPI, etc.). Use this for finding libraries, examples, or open-source implementations. For general web content, use search_web instead.'
• Add error handling guidance to every tool description. Document what happens when providers are down (partial vs. full failure), and suggest recovery steps. Example: 'If a provider fails, results include available data plus per-provider error details. Retry with safe_search=false or fewer providers to diagnose.'
• Expand parameter descriptions with constraint details. For 'providers' param: 'List of provider names (e.g., ["google", "bing", "duckduckgo"]). Call list_providers() to discover available options. Leave empty to use all enabled providers.'
• Add a discovery-focused intro to list_providers description: 'Call this first to see all available search providers, their names, descriptions, and supported tags. Use results to populate the providers or tags parameters in other search_* tools.'
• Introduce a composition guide or decision tree in the server README: 'Use search_web for general queries, search_code for libraries/packages, search_academic for papers, search_finance for stocks/SEC filings, etc.' Embed this intent in tool descriptions.