Both tools have minimal descriptions (under 50 chars) and lack parameter descriptions entirely. Schemas are present but incomplete: 'url' and 'query' parameters have no descriptions, 'css_selector' and 'max_results' lack type info in descriptions. No output schema documented. Error handling returns raw exception messages without recovery guidance. Tool names are acceptable (verb_noun pattern) but descriptions fail to explain WHEN to use each tool or what they return. No input validation guidance. Baseline: A+ tools average 194 chars description + 72 chars per param; these average ~30 chars description + 0 chars per param.

• Add 50-150 character descriptions to each tool explaining WHAT it does, WHEN to use it (vs the other), and what structure it returns. E.g. 'Fetches and converts a web page to Markdown. Use when you need full page content; use websearch for discovery. Returns plain text markdown.'
• Add descriptions to all parameters: 'url' → 'The full HTTP(S) URL to fetch (must start with http:// or https://)', 'css_selector' → 'Optional CSS selector to extract specific elements (e.g. div.content, #main). If omitted, entire page is converted.'
• Document output schema in tool descriptions: 'Returns a single text field containing the markdown-converted content' and 'Returns formatted search results: title, URL, and snippet for each result, separated by newlines.'
• Replace raw exception messages with actionable errors: 'Failed to fetch URL: {url}. Check that the URL is valid and accessible. Retryable.' or 'Search returned no results for query: {query}. Try a simpler query or different keywords.'
• Add constraints to parameters: 'max_results: integer, 1-50 (default 5)' and 'url: must be valid HTTP(S) URL' in both schema and description text.