Single tool 'maps/maps_geocode' has a basic description but lacks critical schema documentation. The tool is registered in google-maps-flow.ts as a string reference ('maps/maps_geocode') with no visible input schema, parameter descriptions, or output schema in the provided source. The description 'Geocode an address to get latitude and longitude coordinates' is only 62 characters and provides minimal LLM guidance on when/how to use it. No parameter documentation, no error handling guidance, no output structure defined. Tool definition appears to be delegated to the external @modelcontextprotocol/server-google-maps package, making it impossible to verify schema quality from this repo alone.

• Add explicit input schema to google-maps-flow.ts showing parameter types, descriptions, and constraints. Example: { address: { type: 'string', description: 'Full or partial address (e.g., "1600 Amphitheatre Parkway, Mountain View, CA"). Required.' } }
• Expand tool description to 120-180 characters: 'Geocode a street address to latitude/longitude coordinates. Accepts full addresses or partial (city, zip). Returns lat, lng, formatted_address, and place_type. Use this to convert user-provided locations into coordinates for distance/direction queries.'
• Document output schema in a comment or JSDoc: 'Returns { latitude: number, longitude: number, formatted_address: string, place_type: string }. Coordinates are WGS84 (EPSG:4326).'
• Add error handling guidance to description: 'If address is ambiguous, the tool returns the most likely match. If no match found, try a broader search (e.g., city name only). Rate limit: 50 requests/second.'
• Uncomment and document the other 5 Google Maps tools (reverse_geocode, search_places, place_details, distance_matrix, elevation, directions) with full schemas and descriptions, or remove them from the commented list to avoid confusion.

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

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