Server has 6 tools with schemas and descriptions, but quality is uneven. Most tools follow the verb_noun naming convention well (greeting, calculator, get_time, generate_image, geocode, get_weather). Descriptions are present but mostly generic Korean translations without LLM-optimized guidance on WHEN to use tools or WHAT they return. Schemas are properly defined with Zod, types are correct, and most parameters have descriptions. However, descriptions lack actionable recovery guidance for errors, and several parameter descriptions are minimal (e.g., 'timeZone' for get_time). No tool annotations (readOnlyHint, destructiveHint) are present despite all tools being marked READ_ONLY. Error handling is basic, no guidance to agents on what to do if a call fails.

• Add readOnlyHint annotation to all 6 tools (all are marked READ_ONLY but the annotation is missing from the server.tool() calls).
• Expand tool descriptions from Korean single words to 50 - 200 character English descriptions that explain WHAT the tool does, WHEN to use it, and WHAT it returns. Example for get_weather: 'Fetch current and forecast weather data for a given latitude/longitude using the Open-Meteo API. Returns temperature, humidity, and weather conditions for up to 16 days. Use this after geocode() to get weather for a location.'
• Document the expected output schema for each tool. E.g., for geocode, add to the tool definition: 'Returns an array of objects with fields: name (string), latitude (number), longitude (number), type (string), importance (number), address (object).'
• Add constraint documentation for 'timeZone' in get_time: 'IANA timezone identifier (e.g., Asia/Seoul, America/New_York, UTC).'
• In generate_image description, note the dependency: 'Requires HF_TOKEN environment variable. Returns image data as base64-encoded PNG.'
• Add error recovery guidance. E.g., in generate_image error handler, return a message like: 'Image generation failed: {error}. Ensure HF_TOKEN is set and you have sufficient API quota. Retry with a simpler prompt or try again later.'
• For geocode, document the default behavior: 'If no results are found, returns a message indicating no matches. Consider retry with a simpler query or broader geographic area.'
• Add idempotentHint annotation to tools that can safely be retried with the same input (all 6 tools qualify).