Server has 19 tools with consistent naming (verb_noun pattern) and complete input schemas. All tools have descriptions and parameter types. However, descriptions are minimal (10-50 chars, well below the 194-char baseline), lack context on WHEN to use tools, and omit error recovery guidance. Output schemas are not documented. No tool annotations (readOnlyHint/destructiveHint) despite 5 destructive/irreversible tools. Parameter descriptions are sparse. Error handling is absent from visible code.

• Expand all tool descriptions to 100-200 chars. Include: WHAT it does, WHEN to use it (vs similar tools), and key return fields. Example: 'Get a single order by UUID or identifier. Use after CREATE_ORDER to check status. Returns: order_id, state (wait|done|cancel), created_at, executed_volume, trades_count.'
• Add tool annotations: mark CANCEL_ORDER, CANCEL_WITHDRAWAL, CREATE_ORDER, CREATE_WITHDRAWAL, CREATE_DEPOSIT_ADDRESS with destructiveHint=true; mark all GET_* and LIST_* with readOnlyHint=true; mark idempotent tools (GET_*) with idempotentHint=true.
• Document output schemas for all tools. For CREATE_ORDER, specify: {order_id: string, market: string, side: 'bid'|'ask', state: 'wait'|'done'|'cancel', created_at: ISO8601, executed_volume: string}. This enables chaining to GET_ORDER.
• Add parameter descriptions for 'currency' (e.g., 'Upbit currency code: BTC, ETH, USDT, etc.'), 'net_type' (e.g., 'Blockchain network: Ethereum, Polygon, Bitcoin, etc.'), and 'market' (e.g., 'Market pair: KRW-BTC, KRW-ETH, USDT-BTC, etc.').
• Implement error handling with recovery guidance. For CREATE_ORDER failures, return: 'Insufficient balance. Call GET_ACCOUNTS to check available balance.' For CANCEL_ORDER on already-closed orders: 'Order already closed (state=done). Cannot cancel. Call GET_ORDER to verify current state.'