19 tools with mostly complete schemas and descriptions, but significant gaps in parameter documentation and error handling. Tool names follow verb_noun convention well (get_, open_, close_, run_). Descriptions average ~150 chars, meeting baseline. However, 8 tools lack parameter descriptions for optional fields (e.g., earnings_calendar 'on_date' has no description; list_recent_signals 'ticker' filter undocumented). No output schemas documented. Error recovery guidance absent. Composition is reasonable, tools are single-purpose, but chaining IDs not always returned (e.g., run_signals persists but doesn't return signal IDs for downstream scoring). Security: no secrets exposed as params (good), but no audit trail or permission gates visible.

• Document output schemas for all 19 tools in the tool_schemas list. Include field names, types, and descriptions. Example: sentiment_aggregate should return {score: number, source_breakdown: object, history_adjusted_score: number}.
• Add descriptions to all optional parameters. For earnings_calendar.on_date, add 'ISO date; defaults to today if omitted'. For list_recent_signals.ticker, add 'Optional ticker filter; if omitted, returns signals for all watchlist tickers'.
• Add error handling guidance to write tools (open_position, close_position, resize_position, run_signals). Example: 'If position already exists, call resize_position instead. If position not found, call get_portfolio_state to see open positions.'
• Return chaining IDs from run_signals. Include signal_ids or a reference to the persisted results so score_signals can retrieve them without a separate lookup.
• Document pagination for list_recent_signals and get_signals. Clarify: 'Returns up to 20 most recent signals by default. Use limit parameter (1-200) to adjust. For large watchlists, paginate in multiple calls.'