Two tools with basic schemas and minimal descriptions. web_search and web_fetch have parameter types defined (string, integer) but descriptions are under 50 chars and lack context on when to use them, prerequisites, or what the LLM should expect. No output schema documented. No error recovery guidance. Parameter descriptions are present but generic. No tool annotations (readOnlyHint). Naming is clear (verb_noun pattern) but descriptions fail to explain WHAT the tool does beyond a one-liner, WHEN to use it, or dependencies.

• Expand tool descriptions to 100-200 chars. Example: 'web_search: Search the web for current information. Returns up to 10 results with title, URL, and snippet. Requires OLLAMA_API_KEY. Use when you need recent data not in training data.'
• Document output schemas explicitly. For web_search, declare: returns string with formatted results (title, URL, content per result). For web_fetch, declare: returns string with page title, content, and up to 10 links.
• Add error recovery guidance. Catch 401/403 errors and return 'Authentication failed. Verify OLLAMA_API_KEY is set and valid.' For 404, return 'URL not found or inaccessible. Try a different URL.'
• Add readOnlyHint=true to both tools in FastMCP registration to signal they are safe to retry and do not modify state.
• Document parameter constraints in descriptions. For max_results, state: 'Maximum number of results to return (1-10, default 5). Capped at 10 by the API.'