Two tools with basic schemas and descriptions, but significant gaps in parameter documentation and output schema clarity. The 'search' tool has a reasonable description (67 chars) and typed parameters with defaults, but 'fetch_content' lacks parameter descriptions entirely. Neither tool documents return types or error recovery guidance. No tool annotations (readOnlyHint, idempotentHint) despite both being read-only. Parameter descriptions are minimal (e.g., 'The webpage URL to fetch content from' is generic). No guidance on rate limiting, timeout behavior, or failure modes visible in tool definitions. Output formatting happens in code (format_results_for_llm) but is not reflected in schema documentation.

• Add explicit parameter description to fetch_content.url: 'The full HTTP(S) URL of the webpage to fetch. Must start with http:// or https://.'
• Document return types for both tools. E.g., search returns 'List of SearchResult objects with title, link, snippet, position fields' and fetch_content returns 'Parsed webpage content as plain text or markdown.'
• Add readOnlyHint and idempotentHint annotations to both tools in the tool definition (FastMCP supports this via tool metadata).
• Enhance error messages with recovery guidance: 'DuckDuckGo rate limit exceeded. Wait 60 seconds before retrying.' or 'URL returned 404. Verify the URL is correct and try again.'
• Document max_results constraint in search description: 'Maximum number of results to return (1 - 100, default 10). Higher values may trigger rate limiting.'

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

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