This server exposes 2 web search tools with partial schema coverage and descriptions. Tool naming is action-oriented (web_search, get_webpage_content), which is good. However, both tools lack comprehensive parameter descriptions, output schemas are not formally documented, and error handling guidance is minimal. The code shows functional implementations but the tool definitions themselves lack the rigor expected of production tools. Descriptions are present but generic (~50-80 chars each). Parameter descriptions exist but are minimal. No documented output structures. No error recovery guidance.

• Document output schema for web_search: return an array of {title: string, snippet: string, url: string, source: string} with a status summary indicating which engines succeeded/failed.
• Document output schema for get_webpage_content: return {content: string, title: string, url: string, word_count: integer} with error details if parsing failed.
• Add explicit enum constraints to 'engine' parameter: declare valid values as ['duckduckgo', 'bing', 'google', 'serpapi', 'tavily'] in the schema and describe fallback behavior.
• Expand parameter descriptions: 'timeout' → 'Request timeout in seconds. Range: 1 - 120. Default: 30. Longer timeouts may be needed for slow connections or large pages.'
• Add recovery guidance to tool descriptions: 'If a search returns no results, try alternative keywords or a different engine. If timeout occurs, reduce max_results or increase timeout parameter.'
• Document result ordering and ranking: 'Results are ranked by relevance (engine-dependent) and limited to max_results (default 10, max 50 to avoid context overload).'
• Clarify caching behavior in web_search description: 'Results are cached for 5 minutes to reduce redundant queries. To force a fresh search, use a slightly different query.'
• Add error categories and recovery actions: distinguish network timeouts (retry with higher timeout), SSL verification failures (use environment flag for testing), blocked IP (use SOCKS proxy).

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

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