This server has clear naming (search_web, fetch_page) and decent descriptions, but lacks critical documentation of output schemas, error handling guidance, and parameter descriptions. Both tools have appropriate input schemas with types, but the output structure is not formally documented, LLMs must infer it from the response. Parameter descriptions are minimal (e.g., 'limit' lacks guidance on when to use lower vs. higher values). Error handling returns JSON errors but offers no guidance for recovery. The tool set is minimal (2 tools) and narrowly scoped to web search/fetch, which is appropriate for the domain but limits composition potential.

• Add formal output schema documentation to both tools. Example for search_web: 'Returns an array of search results. Each result is an object with fields: {url: string (the target URL), title?: string (page title if available), snippet?: string (search snippet if available)}. Array length is limited to the requested limit parameter (1-10).'
• Expand parameter descriptions. For 'limit' in search_web: 'Maximum number of results to return (1-10). Defaults to 5. Use 1-3 for fast, focused searches; 5-10 for comprehensive results. Higher values increase latency and token usage.'
• Add error recovery guidance. When DuckDuckGo search fails: return {error: 'Failed to reach DuckDuckGo: <message>. This is usually temporary, retry in 2-5 seconds, or try search_web with fewer/different keywords if the service is unstable.'}
• Implement tool annotations via server.tool() to signal read-only status. Both tools should use a readOnlyHint annotation once the MCP SDK supports it, or document in descriptions: 'This tool does not modify any data; it is safe to call multiple times with the same parameters.'
• Document timeout and resource limits in tool descriptions. fetch_page has a 15s timeout and 1.5MB cap, state these in the description so LLMs know when to expect timeouts on large/slow sites.
• Migrate from STDIO to HTTP or HTTP+SSE transport to enable remote access and compatibility with hosted MCP clients. STDIO limits adoption to local command-line execution only.
• Add pagination guidance to search_web description: 'This tool does not support pagination. If you need more results, consider refining the query (e.g., adding site: filters or date ranges) rather than increasing limit, as DuckDuckGo HTML parsing is lossy.'