Strong domain-specific tool set with clear, detailed descriptions (avg 180 chars) and comprehensive input schemas using Zod validation. All 10 tools have descriptions and typed parameters with constraints. Naming follows verb_noun pattern (geocode_, property_, price_, estimate_, rent_, dpe_, natural_, commune_, reverse_). Output schemas are not explicitly documented in the source, which is a notable gap. Error handling wraps all tools uniformly but provides only generic 'Error: {message}' responses without recovery guidance. No tool annotations (readOnlyHint, destructiveHint) despite all being read-only operations.

• Document output schemas for all 10 tools. For each tool, add a TypeScript interface or JSON Schema example showing the response structure (e.g., geocode_address returns [{address, lat, lon, insee_code, ban_id}, ...]; property_sales returns {sales: [{price, date, surface_m2, rooms}, ...], total_count}). Include this in tool registration or a separate schema file.
• Enhance error handling with categorization and recovery hints. Instead of generic 'Error: {message}', return structured errors: {isError: true, category: 'not_found'|'invalid_input'|'rate_limit'|'service_error', message: '...', suggestion: 'Try search_users() with a partial name' or 'Retry in 30 seconds'}. This enables agents to self-correct.
• Add tool annotations to all 10 tools. Set readOnlyHint: true in the tool registration for each tool, signaling that they are safe to call speculatively and can be retried without side effects. Example: server.registerTool('geocode_address', {...}, wrap(geocodeAddress), {readOnlyHint: true}).
• Clarify address and location parameter formats in descriptions. For 'address' params, state: 'Free-form address (e.g., "10 rue de la Paix Paris"), street name, or city name. Accepts postal codes and INSEE codes (5-char format like "69123").' For 'location' in rent_estimate, specify: 'Commune name (e.g., "Lyon"), INSEE code (5 chars, e.g., "69123"), or full address.'
• Document result limits and pagination for all tools. Add to descriptions: 'Returns up to [N] results by default. Use limit parameter to adjust (max [M]). For large result sets, results are sorted by [relevance/date/price] and truncated; use offset or next_cursor for pagination.' Ensure property_report, rent_estimate, and estimate_property expose limit controls if they can return multiple items.