Server has 11 tools with basic descriptions and parameter schemas, but significant quality gaps. All tools have descriptions (good), but most are generic and under 100 chars. Parameter descriptions are minimal. No output schemas documented. No error handling guidance. Tools lack semantic clarity, 'fetch_houses' and 'fetch_streets' are vague about what data structure is returned. Calculator tools (add, subtract, etc.) are trivial and add noise. Exchange rate tools lack context on API reliability or rate limits. No tool annotations (readOnlyHint, etc.).

• Document output schemas for all tools. E.g., fetch_houses should return [{id: string, address: string, city: string, street: string, price: number}] with field descriptions.
• Expand tool descriptions to 100-200 chars. Include WHAT (returns list of houses), WHEN (use when you need property listings), and WHAT FIELDS (address, price, owner contact). Reference similar tools: 'Use fetch_streets to get available streets first.'
• Add error handling guidance. E.g., 'If city not found, try search_cities() first. If API rate limit hit, retry after 60 seconds.'
• Remove or relocate calculator tools (add, subtract, multiply, divide, power) to a separate math utility server. They add no domain value to a real-estate/exchange-rate server.
• Add tool annotations: mark all tools with readOnlyHint=true in the tool definition to signal safety to agents and enable optimizations.

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

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