Server has 16 tools with explicit schemas and descriptions visible in src/index.ts. Naming follows verb_noun convention (get_*, create_*, cancel_*). However, parameter descriptions are entirely absent, the schema objects contain only type/enum/required fields with no 'description' key for any parameter. Tool descriptions are present but generic (avg ~50 chars, below the 194-char baseline). No output schemas documented. Error handling not visible in tool definitions. Security concern: set_configuration exposes API credentials as parameters, violating secret-injection pattern. Prediction and trading tools lack guidance on when to use them vs alternatives.

• Add a 'description' field to every parameter in all 16 tool schemas. Example: 'symbol': {'type': 'string', 'description': 'Trading pair symbol (e.g., BTCUSDT for Bitcoin/USDT futures)'}.
• Expand tool descriptions to 150 - 250 chars. Include WHEN to use the tool, what it returns, and how it differs from similar tools. E.g., 'Get the current mark price for a futures contract. Use this for real-time price checks; use get_daily_stats for 24h statistics instead.'
• Move API credentials out of set_configuration parameters. Instead, read apiKey and apiSecret from environment variables (BINANCE_API_KEY, BINANCE_API_SECRET) at server startup. Remove the set_configuration tool or repurpose it for non-sensitive config only.
• Document output schemas for all tools. Add a 'returns' section to each tool definition describing the response structure. Example: 'Returns: {symbol: string, price: string, timestamp: number}'.
• Add a dry-run parameter to create_futures_order and cancel_futures_order. When dry_run=true, validate the order but do not execute it. Return what would happen without side effects, enabling agents to confirm before committing.