Three tools with basic schemas and descriptions, but significant gaps in parameter documentation and error handling. All tools have descriptions (10-20 chars baseline met), but descriptions lack actionable context for LLM selection. Input schemas present but parameters lack descriptions, critical for LLM reasoning. No output schemas documented. No error handling guidance. Tools are read-only (low risk) but lack composition hints and chaining IDs. Naming is clear (verb_noun pattern) but descriptions are generic.

• Add parameter descriptions to all three tools. For 'expression': 'A mathematical expression using +, -, *, /, ** operators and parentheses (e.g., "(2 + 3) * 4"). Max 100 chars.' For 'location': 'City name or location string (e.g., "San Francisco", "London, UK"). Resolves to nearest weather station.' For 'query': 'Search query string (1-500 chars). Use natural language or keywords (e.g., "Python async patterns").'
• Document output schemas in tool descriptions. E.g., calculator: 'Returns {"result": number, "expression": string}.' get_weather: 'Returns {"location": string, "temperature": number, "condition": string, "humidity": number}.' web_search: 'Returns {"results": [{"title": string, "url": string, "snippet": string}], "total_count": number}.'
• Expand tool descriptions to 50-200 chars with WHEN guidance. E.g., calculator: 'Safely evaluate mathematical expressions. Use for arithmetic, algebra, or unit conversions. Supports +, -, *, /, ** and parentheses. Returns numeric result or error message.' get_weather: 'Fetch current weather for a location. Use when user asks about weather, temperature, or conditions. Returns temperature, humidity, and weather condition. Mock implementation for PoC.'
• Add error handling guidance. E.g., 'If location not found, returns error with available nearby locations. If expression is invalid, returns error with syntax hint.' This tells LLMs whether to retry, ask the user, or try a different tool.
• Add parameter constraints. For calculator, document that expressions must be valid Python math syntax. For get_weather and web_search, add min/max length constraints and note that results are paginated (if applicable) or capped at N results.

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

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