mcp-omniserp presents a functional search tool suite with clear naming conventions and consistent parameter schemas across all 12 tools. However, tool descriptions are uniformly brief (15-30 characters), falling well below the 194-char baseline for production tools. Parameter descriptions are present but generic, lacking actionable context about constraints, formats, or when to use each specialized search variant. Output schemas are not visible in the provided source code, only input schemas are documented. The tool set has good verb-noun naming (google_search*, webpage_scrape) and organized around single concerns, but lacks guidance on error recovery, pagination behavior, and the functional differences between overlapping search tools (e.g., google_search vs google_search_news). Security handling for API keys is well-designed (keyring/VaultGuard integration), but this is server-side and not reflected in tool parameters, which is correct.

• Expand each tool description to 100-200 characters. Answer: WHAT does this tool do? WHEN should the LLM choose it over similar tools? WHAT resource type does it search (web pages, news, academic, shopping)? Example: 'Search Google Scholar for peer-reviewed academic papers. Use this for research queries, citations, and scholarly content. Returns ranked articles with titles, abstracts, and publication details.'
• Add parameter constraints to descriptions. For 'country', document: 'ISO 3166-1 alpha-2 country code (e.g., US, GB, FR) for search localization. Omit for global results.' For 'language', document: 'ISO 639-1 language code (e.g., en, fr, de). Omit for default locale.' For 'numResults', add: 'Number of results to return (1-50, default 10). Capped at 50 to prevent token exhaustion.'
• Document output schema for each tool. Include in description or as a separate block: what fields are returned (title, url, snippet, source, date)? Is pagination supported (next_cursor, total_count)? What format is returned (JSON object, array of objects)?
• Add error recovery guidance. Example: 'If rate-limited, wait 60 seconds and retry. If country code invalid, fallback to global search. If timeout, check network and retry once.'
• Reduce tool fragmentation by consolidating descriptions that clarify intent. E.g., rename google_search_news to 'search_news' with description: 'Search Google News for current news articles. Returns recent articles, sources, publication dates. Use for recent events and breaking news.' Similar clarity for Scholar, Shopping, Places.