Two tools with basic schemas and descriptions, but significant gaps in parameter documentation and output schema clarity. Tool names follow verb_noun convention (get_, check_). Descriptions exist but are brief (50-80 chars, below the 194-char baseline). Input schemas present with types and enums, but missing descriptions for several parameters. No documented output schemas. Error handling and recovery guidance absent. Composition is reasonable, tools are single-purpose and chainable via symbol/firm parameters.

• Document output schemas for both tools. Example for get_upcoming_events: 'Returns array of {name, date, time, datetime (ISO 8601), impact (critical|high|medium), instruments (array), description, avgMovePoints (number|null), recurring (weekly|monthly)}'.
• Add descriptions to all parameters. For 'instruments' in get_upcoming_events: 'Array of futures symbols to filter by (e.g., ES, NQ, CL, 6E, ZB, GC). If omitted, returns all instruments.' For 'symbol' in check_trading_restriction: 'Futures symbol being traded (e.g., ES, NQ, CL). Optional; if omitted, checks restrictions for all symbols.'
• Expand tool descriptions to 100 - 200 chars. For check_trading_restriction: 'Check if a prop firm's news trading restriction is active now or within a specified time window. Returns whether trading is blocked and the restriction window (minutes before/after events). Use this before entering positions around high-impact economic events.'
• Add error handling guidance. If firm is invalid, return: 'Unknown firm: {firm}. Valid firms: apex, ftmo, topstep, bulenox, myfundedfutures, tradeday, earn2trade.' If symbol is invalid, return: 'Unknown symbol: {symbol}. Valid symbols: ES, NQ, CL, 6E, ZB, GC, NG, QM.'
• Clarify parameter constraints in descriptions. For 'days_ahead': 'Number of days to look ahead (1 - 365, default 7). Larger values may return hundreds of events.' For 'minutes_buffer': 'Minutes ahead to check (0 - 120, default 0). Use 5 - 10 to anticipate upcoming restrictions.'