Three tools with clear verb-noun naming (get_stock_analysis, get_current_weather, get_forecast) and reasonable descriptions (100-150 chars). All tools have input schemas with type definitions and parameter descriptions. However, output schemas are not documented, LLMs cannot predict return structure. Error handling returns structured {ok, error} but lacks recovery guidance. No tool annotations (readOnlyHint, idempotentHint). Parameter descriptions are minimal (10-30 chars) and lack format/constraint details. No pagination support despite weather forecast accepting 'days' parameter. Missing documentation of what fields are returned and their types.

• Document output schemas for all three tools. Specify field names, types, and presence (required vs optional). Example: get_stock_analysis returns {ok: bool, symbol: string, price_current: float, headlines: string[], ...}.
• Expand parameter descriptions to 50-100 chars with format/constraint details. E.g., 'City name (e.g., London, New York). Resolved via Open-Meteo geocoding; partial matches supported.'
• Add tool annotations: set readOnlyHint=true on all three tools to signal they are safe for autonomous execution.
• Enhance error messages with recovery guidance. E.g., 'Stock service timed out for AAPL (30s). Retry in 5s or try a different ticker.' instead of bare timeout message.
• Add min/max constraints to get_forecast 'days' parameter in schema and description: 'Number of days to forecast (1-7, default 3)' with explicit validation.