Server has 15 tools with basic descriptions and input schemas present. However, critical gaps undermine quality: (1) Parameter descriptions are minimal or missing context (e.g., 'symbol' lacks format guidance like 'BTCUSDT'); (2) Output schemas are not documented, responses are inferred from code but not formally declared; (3) No error handling guidance, tools lack recovery hints for common failures (invalid symbol, insufficient balance, API errors); (4) Destructive tools (emergency_close_all, enter_long/short) lack confirmation patterns or dry-run support; (5) Tool descriptions are functional but lack WHEN/WHY context for LLM selection. Naming is clear and verb-based (get_, find_, enter_, close_), which is a strength. Average tool score: 52/100.

• Add formal output schema documentation to every tool. Use JSON Schema or a structured format to declare response fields, types, and required keys. Example: get_current_price returns {symbol: string, price: string, message: string}.
• Implement confirmation pattern for destructive tools. Add a 'dry_run' parameter (default false) to enter_long, enter_short, close_position, and emergency_close_all. When true, return what would happen without executing. Require explicit confirmation before real execution.
• Enhance parameter descriptions with format constraints. For 'symbol', add: 'Trading pair in uppercase format (e.g., BTCUSDT, ETHUSDT). Must be a valid Binance pair.' For 'quantity', add: 'Amount to trade (positive number, minimum 0.001, maximum 10000).'
• Add error handling guidance to tool descriptions. Document common failure modes and recovery steps. Example: 'If symbol is invalid, returns error with list of available pairs. If balance insufficient, returns required balance and current balance.'
• Clarify tool selection context in descriptions. For find_hot_pairs and find_breakouts, add: 'Use find_hot_pairs to identify high-volume movers. Use find_breakouts for price action near resistance levels. Both scan the full market; use find_hot_pairs for volatility, find_breakouts for momentum.'

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

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