Server has 4 well-named, read-only tools with clear descriptions and proper input schemas using Pydantic Field annotations. All tools follow verb_noun naming (geocode, reverse_geocode, calculate_distance, distance_between_places). Descriptions are concise (34-89 chars) and state what each tool does. Input parameters have type constraints (min/max for coordinates, limit bounds). However, output schemas are not formally documented, responses are inferred from code inspection. Error handling is minimal; no recovery guidance or actionable error messages. Missing tool annotations (readOnlyHint present implicitly via Risk field, but not in MCP schema). No pagination support despite geocode returning lists.

• Add explicit output schema documentation to each tool. E.g., geocode returns [{address: string, latitude: number, longitude: number, name: string|null}]. Include this in docstrings or as a structured response_schema field.
• Implement pagination for geocode: add a 'page' or 'offset' parameter, return a 'total' count, and document the limit (currently 10 max). This prevents context window exhaustion on ambiguous addresses.
• Add error handling with recovery hints. E.g., if geocoding fails, return {error: 'Address not found. Try a broader location (city/country) or check spelling.', retryable: true}. Distinguish network errors from not-found.
• Expose readOnlyHint in tool definitions via MCP schema. All four tools are read-only; mark them explicitly so agents know they are safe to retry.
• Enhance distance_between_places description: 'Geocodes both addresses, then calculates distance. Returns address, coordinates, and distance in multiple units. If either address is ambiguous, returns the first match.'

Inferred effective spec: 2026-07-28+.

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