Server provides 4 tools with basic naming and schema coverage. Tool names follow verb_noun pattern (web_search, news_search, image_search, video_search), which is good. However, descriptions are generic and repetitive across all tools. Parameter descriptions are minimal, 'A detailed search query string' and 'Number of results to return (default: 5)' lack context about constraints, format, or when to use each tool. Output schemas are not documented, callers cannot predict what fields to expect in the response (title, snippet, URL are mentioned in docstring but not in a formal schema). All tools are read-only (appropriate risk classification), but there is no guidance on error handling, recovery steps, or result limits. The tools are simple wrappers around DuckDuckGo with identical structure across all four, which increases the risk of LLM confusion when selecting between them.

• Add distinct, LLM-optimized descriptions for each tool. Example for web_search: 'Search general web content (articles, blogs, documentation). Returns title, snippet, and URL. Use this for technical information, current events outside news, and reference material.' For news_search: 'Search news articles only (recent stories, breaking news). Returns headline, source, publication date, snippet, and URL. Use when the user explicitly asks for news or current events.' Similar distinctions for image_search and video_search.
• Document output schema explicitly. Add a 'Returns' section to each docstring: e.g., 'Returns: list[{"title": str, "url": str, "snippet": str, "source": str (news_search only), "date": str (ISO 8601, news_search only)}]'
• Specify min/max bounds for num_results parameter. Example: 'Number of results to return (default: 5, min: 1, max: 50). Requesting more than 50 results may increase latency and token consumption.'
• Add error handling guidance in descriptions. Example: 'If no results are found, the tool returns an empty list. If the search times out (>5s), an error is raised. Retry once with a simpler query; if it fails again, report that search is unavailable.'
• Document result limits and indicate when pagination is needed. If DuckDuckGo returns max 100 results, state this and explain the consequence of requesting more.
• Distinguish the four tools more clearly in naming or grouping. Consider renaming to make the search scope more obvious: search_general_web, search_news_articles, search_images, search_videos. Or add prefix: 'web_' prefix is already there, but 'news_search' could be 'web_search_news' for consistency.

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

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