Web Forager has 4 search/fetch tools with adequate naming and mostly complete schemas. Tool names are action-oriented (duckduckgo_search, web_fetch, duckduckgo_news_search, search) and follow verb_noun convention. Descriptions are present but vary in quality, some are detailed with guidance ('search news fixtures, errors not empty results'), others are minimal ('Search DuckDuckGo for the given query'). All tools have parameter schemas with type information and descriptions. However, output schemas are not documented, and some parameter descriptions lack depth. The 'search' tool appears redundant with 'duckduckgo_search', violating the composition principle of avoiding multiple tools doing the same thing. No explicit error handling guidance in descriptions. Tool annotations are present (readOnlyHint=true) which aligns with current spec patterns.

• Remove the 'search' tool entirely. Keep 'duckduckgo_search' as the canonical web search tool. Consolidate all search logic under one function to reduce LLM ambiguity.
• Document output schemas for all tools. Add to each tool description: 'Returns: list of dicts with keys [title, url, snippet, date] for search tools' or 'Returns: string in markdown format' for web_fetch.
• Convert 'safesearch' and 'output_format' parameters to enums with explicit allowed values: safesearch: ['on', 'moderate', 'off'], output_format: ['json', 'text']. This prevents hallucinated values.
• Add error handling guidance to descriptions: 'If a search returns no results, try broader query terms. If web_fetch times out, set allow_jina=False for direct-only access.'
• Improve the 'search' tool description (if retained) to explain its relationship to 'duckduckgo_search' or remove it entirely to avoid tool duplication.
• Document parameter constraints for 'max_results': specify min and max (e.g., 'integer, 1 - 50, default 5').
• For web_fetch, clarify what happens when a page is unavailable and what error message is returned so LLMs know when to retry or escalate.