Server has 20 tools with consistent verb-noun naming (create_, get_, update_, add_, remove_, confirm_, pay_, filter_, search_). All tools have descriptions in Korean, ranging 20 - 200 chars. Input schemas are present with type definitions for all parameters. However, descriptions lack English translations, making them inaccessible to non-Korean-speaking developers. Parameter descriptions are minimal (often just field names in Korean). Output schemas are not documented in the tool definitions, responses are inferred from domain models (CartResponse, MenuDetail, etc.) but not explicitly declared to the LLM. Error handling is present in code (SpringApiError, ValidationError) but not surfaced in tool descriptions. No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite clear risk levels (WRITE, DESTRUCTIVE, IRREVERSIBLE). Composition is strong, tools chain well (create_session → add_cart_item → confirm_order → request_payment). Idempotency is addressed in code comments (e.g., cart lock retry logic) but not documented in tool descriptions.

• Translate all tool and parameter descriptions to English. Use clear, concise language (50 - 200 chars per tool, 30 - 80 chars per parameter) optimized for LLM reasoning. Example: 'tool_create_session' → 'Start a new order session. Returns session_id required for all subsequent cart and order operations. order_type must be DINE_IN (in-store) or TAKEOUT (delivery).'
• Document output schemas explicitly in tool definitions. For each tool, add a 'returns' field describing the response structure. Example for tool_get_menus: 'Returns array of menu objects with fields: menu_id (int), name (string), price (int), category_id (int), description (string).'
• Add tool annotations to all tools. Mark read-only tools with readOnlyHint=true (get_*, list_*, search_*). Mark destructive tools with destructiveHint=true (clear_cart, confirm_order, request_payment). Mark idempotent tools with idempotentHint=true (add_cart_item with retry logic).
• Enhance parameter descriptions with constraints and examples. For 'option_ids' in tool_add_cart_item: 'Array of option IDs (integers) from tool_get_menu_detail. Empty array if no options. Example: [101, 102].' For 'exclude_allergies' in tool_filter_menus: 'Comma-separated allergy codes (MILK, EGG, WHEAT, SOY, PEANUT, WALNUT, PINE, SHRIMP, CRAB, SQUID, CLAM, BEEF, PORK, CHICKEN, PEACH, TOMATO, BUCKWHEAT). Example: MILK,EGG'.
• Document error recovery paths in tool descriptions. Example for tool_add_cart_item: 'May return 409 CART_LOCK_ACQUIRE_FAILED if concurrent requests conflict, safe to retry after 300ms. Returns 400 if menu_id invalid or option_ids do not match menu. Returns 502 if backend schema mismatch.'

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

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