5 tools with explicit schemas and descriptions visible in src/ddg_mcp/server.py. All tools have input schemas with required/optional fields properly specified. Descriptions present but generic and do not explain WHEN to use each tool vs alternatives or what state changes occur. Parameter descriptions are present but minimal (avg 30-50 chars). No output schemas documented. Tools follow verb_noun naming but descriptions lack depth. One prompt feature implemented but shallow. No error handling guidance visible in code. Overall in the C range, definitions are structurally present but lack LLM optimization and production-grade guidance.

• Expand tool descriptions to 150-250 chars. Include WHEN to use (e.g., 'Use for general web content, news articles, images, or videos. ddg-text-search returns web pages; ddg-image-search returns image URLs; ddg-news-search returns recent news; ddg-video-search returns video metadata.').
• Document output schemas for all 5 tools in list_tools(). Describe what fields each tool returns (e.g., 'Returns array of {title: string, href: string, body: string} for text search').
• Add error handling: validate 'keywords' is non-empty, handle API timeouts with retry guidance, catch and transform raw DuckDuckGo errors into actionable messages (e.g., 'No results found for query. Try broadening keywords or removing filters.').
• Rename 'keywords' parameter to 'query' for search tools and 'message' or 'prompt' for ddg-ai-chat to match semantic intent and reduce LLM confusion.
• Add pagination to search tools: accept 'offset' (default 0) and 'limit' (default 10, max 50), return 'total_results' count and 'has_more' boolean so agents can page through results.
• For ddg-ai-chat, add explicit guidance on model selection: 'gpt-4o-mini for general queries, llama-3.3-70b for reasoning, claude-3-haiku for speed, o3-mini for complex analysis, mistral-small-3 for lightweight tasks.'
• Document max result limits in tool descriptions. E.g., 'Returns up to max_results items (default 10). For large result sets, use pagination or narrow filters (region, timelimit, safesearch).'
• Add per-parameter constraints to descriptions: 'region must be valid DuckDuckGo region code (e.g., wt-wt, us-en, uk-en)', 'max_results must be 1-100', etc.