Server has 10 tools with consistent naming (verb_noun pattern: getPrices, getOrderbook, placeOrder, etc.) and descriptions present for all tools and parameters. However, descriptions are often terse (10-50 chars) and lack actionable context for LLM selection. Input schemas are visible and typed, but output schemas are undocumented, tools return String (JSON serialized) with no declared structure. Error handling is minimal; no recovery guidance or categorization. Trading tools support dry-run (good), but no explicit permission gates or audit trail declarations. Parameter constraints (e.g., 'maximum 200' symbols, 'KRW or USD') are stated in descriptions but not formalized as enums or JSON Schema constraints.

• Document output schemas for all tools. E.g., placeOrder returns {status: 'DRY_RUN'|'PLACED'|'REJECTED'|'UNKNOWN', orderId?: string, reason?: string}. Declare this in tool metadata or a separate schema registry.
• Expand descriptions to 50 - 150 chars with WHEN/WHY context. E.g., 'getOrderbook: Returns bid/ask depth for a single symbol. Use this to assess liquidity before placing large orders. Complements getPrices (current price only).'
• Formalize parameter constraints as JSON Schema. Add maxLength, enum, pattern, or minimum/maximum to the input schema. E.g., currency: {type: 'string', enum: ['KRW', 'USD']}.
• Add error handling guidance to placeOrder and cancelOrder. Document possible error statuses (REJECTED, UNKNOWN) and recovery steps. E.g., 'If status=REJECTED, check the reason field and retry with adjusted parameters or call getBuyingPower to verify funds.'
• Declare permission scopes for trading tools. Add a 'scopes' field to placeOrder and cancelOrder metadata: ['write:trading', 'read:account']. This enables least-privilege agent configuration and audit trails.