Server provides 10 well-scoped read-only tools with complete input schemas and clear descriptions. All tools have proper JSON Schema definitions with required fields and type annotations. Descriptions are concise (10 - 200 chars) and action-oriented. However, output schemas are not documented, LLMs cannot predict response structure for downstream chaining. Parameter descriptions are minimal (e.g., 'ISO date' lacks format guidance). No error handling guidance, no recovery hints, and no per-parameter constraints (enums, ranges). Tools are well-named with action verbs (sunrise_sunset, moon_phase, geocode) but lack composition hints for multi-step workflows.

• Document output schemas for all 10 tools. Include field names, types, and nesting. E.g., sunrise_sunset returns {date: string, lat: number, lon: number, sunrise: string (ISO 8601), ...}. This enables LLMs to plan downstream calls.
• Add format constraints to parameter descriptions. Replace 'ISO date' with 'ISO 8601 date format YYYY-MM-DD (e.g., 2024-12-25). Defaults to today if omitted.' Replace 'country' with 'ISO 3166-1 alpha-2 country code (e.g., US, CA, GB, JP). Case-insensitive.'
• Add error handling guidance. Document which tools call external APIs and what failures are possible. E.g., 'geocode may fail if Nominatim is rate-limited (HTTP 429), retry after 1 second. Returns empty results if address not found, suggest alternative spellings.'
• Add tool composition hints in descriptions. E.g., geocode: 'Call this first if you only have an address. Returns lat/lon for use with distance, elevation, or timezone_of.' distance: 'Requires lat/lon from geocode or reverse_geocode.'
• Validate and document parameter constraints. Add enum examples for country codes (US, CA, GB, JP, etc.). Add min/max for numeric lat/lon (-90 to 90, -180 to 180). Add regex pattern for date format in schema.