14 tools with consistent verb-noun naming (get_*, place_*, cancel_*, edit_). All have descriptions (10-50 chars, below ideal 50-200 baseline). Input schemas present for 9/14 tools with typed parameters. Output schemas not documented. Error handling minimal, no recovery guidance or categorization. Missing parameter descriptions for several tools (e.g., get_account_summary, get_positions, get_orders, get_order_history, get_trades, cancel_all_orders lack visible input schemas). No tool annotations (readOnlyHint/destructiveHint). Composition is sound, tools are single-responsibility and chainable via IDs.

• Add input schemas to get_account_summary, get_positions, get_orders, get_order_history, get_trades, cancel_all_orders. Even if they accept no parameters, declare an empty object schema for consistency.
• Expand tool descriptions to 100-200 chars. Include WHEN to call (e.g., 'Call before placing orders to verify available balance and open positions'), WHAT it returns (e.g., 'Returns current balance, margin, and list of open positions'), and any prerequisites.
• Document output schemas for all tools. E.g., place_order should return {order_id: string, status: string, price: number, amount: number}. This enables agents to chain calls (place_order → edit_order using returned order_id).
• Add tool annotations: mark get_* tools with readOnlyHint=true; mark place_order, edit_order with destructiveHint=true; mark cancel_order, cancel_all_orders with destructiveHint=true and idempotentHint=true (safe to retry).
• Add error handling to place_order and edit_order: return actionable errors like 'Invalid instrument: BTC-PERP not found. Valid instruments: BTC-PERPETUAL, ETH-PERPETUAL. Call get_instruments() to list all.' Include validation for price (must be positive), amount (must be > 0), and side (must be buy|sell).

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

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