Server has 6 tools with basic descriptions and input schemas visible in main.go. All tools are READ_ONLY and follow verb_noun naming (geocode, reverse_geocode, directions, distance_matrix, search_places, get_usage). Descriptions are present but brief (10-60 chars), below the 50-200 char LLM-optimized baseline. Input schemas use Go struct tags with jsonschema annotations, providing type info. However, parameter descriptions are minimal, output schemas are not documented, and error handling lacks recovery guidance. No tool annotations (readOnlyHint, etc.) despite all being read-only. Missing pagination for search_places despite potentially returning many results.

• Expand tool descriptions to 50-200 chars. Example: 'geocode' → 'Convert a street address to latitude/longitude coordinates. Use this to locate places before calling directions or distance_matrix. Returns formatted address, coordinates, and place ID.'
• Document output schemas in tool metadata. For geocode: {formatted_address: string, latitude: number, longitude: number, place_id: string}. For search_places: {results: [{name, address, rating, lat, lng, place_id}], total_count: number}.
• Add pagination to search_places: accept limit (1-50, default 20) and offset parameters; return total_count and next_offset. Cap results at 20 per call to prevent context bloat.
• Enhance error messages with recovery guidance. E.g., 'Geocoding failed: ZERO_RESULTS. Try a more specific address (e.g., include city/state) or use search_places() to find the location first.'
• Add readOnlyHint: true to all tool definitions in the MCP server registration to signal these are safe, idempotent calls.