Server has 16 tools with complete input schemas and descriptions. Naming follows verb_noun pattern (get_, place_, cancel_, etc.). Descriptions are present but brief (avg ~60 chars, below the 194-char baseline). Parameters have types and descriptions. Critical gaps: no output schemas documented, no error handling guidance, no parameter constraints (enums for order_type, interval), no pagination for list-like tools (get_fills, get_candles), and no idempotency/confirmation patterns for destructive WRITE tools. Security concern: private key loaded from environment without explicit secret-injection pattern documentation.

• Document output schemas for all tools. For get_user_state, specify fields like positions[], balances{}, orders[]. For get_candles, return [{timestamp, open, high, low, close, volume}]. This enables LLM planning.
• Add enum constraints: order_type=['Limit', 'Market'], interval=['1m', '5m', '1h', '1d']. Add numeric bounds: leverage (1-20), sz (>0), limit_px (>0). Replace free-form descriptions with formal constraints.
• Expand tool descriptions to 100-150 chars. Include WHEN to use: 'Get all open orders for the account. Call this before placing a new order to check for conflicts.' Add dependency hints for multi-step workflows.
• Implement pagination for get_fills and get_candles: add offset/limit params, return total_count, document max result limit (e.g., 100 per call). Cap default limit at 20-50.
• Add error recovery guidance in tool descriptions for WRITE tools: 'On timeout, call get_open_orders() to verify if the order was placed before retrying.' Document which errors are retryable vs fatal.

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

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