Three tools with complete schemas and descriptions, but significant gaps in parameter documentation and output schema clarity. web_search and multi_search have good descriptions (150-180 chars, within baseline 194 avg), but parameter descriptions are sparse or missing. clear_cache lacks meaningful description (18 chars, below 20-char floor). No output schema documented for any tool. Error handling and recovery guidance absent. Naming follows verb_noun convention (web_search, multi_search, clear_cache) but lacks specificity about what 'search' returns or when to use multi_search vs web_search.

• Expand clear_cache description to 50-100 chars: 'Clear the in-memory search results cache to free memory or force fresh results on next search. Useful after long sessions or when SearXNG index updates.'
• Document output schema for web_search: return object with fields {query: string, resultsCount: number, results: [{title, url, content, publishedDate, domain}]}. Include in tool description or as a separate schema block.
• Add parameter constraints: language enum (en|es|fr|de|...) or regex pattern; categories enum (general|news|science|...); timeRange already has enum but should document what each value means (day=last 24h, week=last 7d, etc.).
• Add error handling examples in description: 'Returns error if SearXNG is unreachable (check server URL) or if query is empty. Retry with shorter query if timeout occurs.'
• Clarify multi_search use case: 'Use when you need results for 3+ related queries in parallel. For 1-2 queries, use web_search twice, simpler and same latency.'