Three tools with basic verb-noun naming (geocode_address, check_residency, get_district). Descriptions present but generic (avg 150 chars, below 194-char baseline). Input schemas visible with single 'address' parameter, but lack type specificity and validation constraints. No output schemas documented. No error handling guidance. No tool annotations. Parameters lack enums, ranges, or format constraints despite accepting free-form strings that fail silently on abbreviations.

• Add explicit output schemas to all three tools. Document fields: lat (number), lng (number), matched_address (string), is_resident (boolean for check_residency), district_name (string for get_district), and any metadata (count, note).
• Replace free-form 'address' parameter with constraints: add minLength: 5, maxLength: 200, and a description explaining expected format ('Street address with optional city/state, e.g., "1600 Pennsylvania Avenue NW, Washington DC").
• Implement actionable error responses. Instead of 'No address match found', return: 'Address not found. Try: (1) use full street name (e.g., Pennsylvania Avenue instead of Penn Ave), (2) include city/state, (3) call search_addresses() for suggestions.'
• Add tool annotations: readOnlyHint: true and idempotentHint: true to all three tools so LLMs know they are safe to retry and do not modify state.
• Separate parameter descriptions from implementation notes. Rewrite geocode_address description to: 'Geocode a street address to latitude/longitude coordinates. Returns all matching addresses if multiple are found (e.g., same street in different quadrants). Use check_residency to verify city boundary; use get_district to find ward/district.' Remove 'try variations if needed', that is internal logic.

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

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