Server implements 2 tools with basic definitions but significant gaps in production readiness. Tool names follow verb_noun pattern (search, fetch_web_content) which is correct. However, descriptions are minimal (16-34 chars), parameter descriptions are sparse or missing entirely, output schemas are not documented, and error handling guidance is absent. The 'search' tool description 'Search the web using DuckDuckGo' is only 31 chars, below the 10-1024 char guideline and lacks context on when to use it vs alternatives. The 'fetch_web_content' tool (34 chars) similarly lacks detail on what it returns, when to call it, or how it relates to search. Input schemas show parameter types but lack descriptions for the parameters themselves, violating pattern:tool-description. No output schema is visible in the provided code. Per-tool scores average to 42, placing this in the D range (50-59 boundary) for definition quality.

• Expand 'search' tool description from 31 to ~150 chars: 'Search the web using DuckDuckGo. Returns up to 20 ranked results with title, URL, and snippet. Use this to find general information, news, or resources. Returns empty results if no matches found.'
• Expand 'fetch_web_content' tool description: 'Fetch and extract the main text content from a URL. Removes navigation, ads, and metadata. Returns the cleaned article/page text, title, and URL. Use this after search() to read the full content of a promising result.'
• Add parameter descriptions: For 'search' → 'The search query as a natural language phrase or keywords (e.g., "Python async programming"). Max 500 chars.' For 'fetch_web_content' → 'The full HTTP/HTTPS URL to fetch (must start with http:// or https://). Max 2048 chars.'
• Document output schemas for both tools. Example for search: '{"results": [{"title": string, "url": string, "snippet": string, "rank": number}], "total_results": number}'. For fetch_web_content: '{"url": string, "title": string, "content": string, "success": boolean, "error": string}'
• Add error handling guidance: For search: 'If no results returned, try with simpler keywords or check query for typos.' For fetch_web_content: 'If content extraction fails, the URL may require JavaScript rendering or authentication.'
• Add pagination to 'search' tool: Accept optional 'limit' (1-50, default 10) and 'offset' (default 0) parameters. Return 'total_results' in response to signal if more results exist.
• Add parameter constraints: 'url' parameter should include regex pattern or explicit format validation notes: 'Must be a valid HTTP(S) URL. Localhost and file:// URLs not supported.' Validate before fetching to return clear error messages.