16 tools with basic schemas and descriptions, but significant gaps in parameter documentation and output schema clarity. Most tools have 1-4 parameters with type info, but descriptions are minimal (10-50 chars) and lack actionable guidance. No error handling patterns, no output schemas documented, no tool annotations. Naming is verb-first and clear (getMarkets, createOrder, cancelAllOrders), but parameter descriptions are sparse and many lack format/constraint details. No evidence of idempotency hints, confirmation patterns for destructive ops, or recovery guidance.

• Document output schemas for all 16 tools. Specify field names, types, and which fields are required. E.g., getMarkets should return {markets: [{symbol: string, baseAsset: string, quoteAsset: string, ...}], total: number}.
• Convert interval, side, tif, and trigger_price_type parameters to enums instead of free-form strings. E.g., interval: enum ['1m', '5m', '15m', '1h', '2h', '4h', '1d', '1w'].
• Expand parameter descriptions to 50-100 chars with format/constraint details. E.g., 'price: Order price as decimal string (e.g., "12345.67", max 8 decimals)' instead of 'Order price as decimal string'.
• Add error handling guidance to tool descriptions. E.g., createOrder: 'Returns error if account has insufficient balance or order violates risk limits. Retry is safe if error is transient (network timeout); not safe if error is validation (invalid symbol).'
• Add confirmation/dry-run support for destructive tools (createOrder, cancelOrder, cancelAllOrders, deposit). E.g., createOrder should accept a 'dry_run: boolean' parameter to validate without executing, or return a confirmation_required response.