Single tool with reasonable naming and basic schema present, but critical gaps in description quality, output schema documentation, and error handling guidance. The tool name 'search_restaurants' follows verb_noun convention and is clear. Input schema is visible with types and descriptions for all parameters. However, the tool description (107 chars) falls short of best practices, and there is NO documented output schema, LLMs cannot plan downstream calls without knowing what fields to expect. Error handling returns JSON blobs with 'success' and 'error' fields, but provides no recovery guidance. Parameter descriptions are present but lack detail on valid ranges, constraints, or dependency hints. No mention of pagination, result limits, or idempotency. The codebase shows basic error logging but no strategic error classification.

• Expand tool description to 150-250 chars. Example: 'Search for restaurants by location, cuisine type, and radius. Returns name, address, rating, and phone for each restaurant. Use this to find dining options when planning a trip. Supports lat/lon and city name formats.'
• Document the output schema explicitly. Add a docstring section like: 'Returns: {success: bool, location: str, total_results: int, restaurants: [{name: str, address: str, rating: float, phone: str, place_id: str}]}'
• Add min/max constraints to parameter descriptions. Example: 'radius_km: Search radius in kilometers (1-50, default 10)' and 'max_results: Maximum number of results to return (1-20, default 10)'
• Implement pagination. Add 'page: int (default 1)' parameter and return 'has_more: bool' + 'next_page: int' in response. See pattern:paginated-result.
• Enhance error messages with recovery hints. Catch common errors and return: 'Invalid location format. Try "New York, NY" or use coordinates "40.7128,-74.0060".' instead of raw exception text.
• Implement result cap. Hard-limit to 20 restaurants per search and state this in the description: 'Returns up to 20 results. Use pagination to fetch more.'
• Add tool annotation hints via MCP. Mark the tool with readOnlyHint=true since it only searches and does not modify state.
• Document idempotency guarantee. Confirm: 'Repeated calls with the same location and filters return consistent results (except for real-time rating changes). Safe to retry on transient errors.'

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

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