Server has 5 tools with complete input schemas and descriptions. Naming follows verb_noun convention (search_*, get_*). Descriptions are present but brief (40-80 chars, below the 194-char baseline). All parameters have types and descriptions. However, output schemas are not documented in the source code, and error handling guidance is absent. No tool annotations (readOnlyHint, destructiveHint) despite all tools being read-only. Parameter descriptions lack format constraints and dependency hints.

• Document output schemas for all tools. Specify fields returned by search_locations (e.g., location_id, name, type), search_properties (e.g., ad_id, title, price, rooms, size), and detail/stats tools. Include field types and whether they are always present.
• Expand tool descriptions to 100-200 characters. Add WHEN to use (e.g., 'Call this after search_locations to get full property details'), prerequisites, and dependency hints. Example: 'Get full property details by ad ID. Requires ad_id from search_properties or get_ad_details_by_url.'
• Add readOnlyHint: true to all tool definitions in the registration code (tools/locations.go, tools/search.go, tools/detail.go, tools/stats.go) to signal safety to agents.
• Add format constraints to parameter descriptions: 'prefix' (1-50 chars), 'page' (min 1), 'items_per_page' (1-50, default 20), 'min_price'/'max_price' (non-negative numbers), 'min_rooms'/'max_rooms' (positive integers).
• Add error recovery guidance to descriptions. Example: 'If location not found, try search_locations with a shorter prefix or different spelling. If API rate limit hit, retry after 60 seconds.'