openInvest exhibits moderate-to-good definition quality with 21 tools covering portfolio analysis, committee voting, and trade logging. Strengths: most tools have clear, action-oriented names and substantive descriptions (100-250 chars typical); input schemas are present with typed parameters; risk classifications (READ_ONLY/WRITE) are declared. Weaknesses: inconsistent schema completeness (some tools lack explicit type declarations in source); output schemas are undocumented in the tool definitions themselves (only described in prose); Chinese-language descriptions in tools 17-21 reduce LLM clarity; no parameter validation guidance (ranges, patterns, or constraints); error handling is not specified in any tool definition; descriptions lack 'WHEN to use' context and 'WHAT it returns' detail expected by LLMs. The tool set is well-scoped (one action per tool: status, strategy, history, etc.) but could benefit from explicit output schema registration and actionable error messages.

• Translate all Chinese tool descriptions to English (or provide English-first bilingual versions). Tools 17-21 are currently opaque to English-speaking LLMs.
• Register explicit JSON Schema output schemas for all 21 tools. Document the structure of status, run_committee, history, etc. so LLMs can plan downstream calls.
• Add min/max constraints to all numeric parameters: history(n: 1-100), decisions(days: 1-365), adjust_cash(amount: actual min/max), query_dreaming_insights(top_k: 1-50).
• Add format constraints: add_news_source(url: format=uri), post_trade(timestamp: format=date-time), run_committee(symbol: pattern='^[A-Z0-9.=X]+$' for yfinance tickers).
• Document error cases and recovery paths in tool descriptions. E.g., 'If symbol is invalid, returns error listing available tickers.' Or 'If cash insufficient, suggests adjust_cash tool.'
• Add scope declarations to WRITE tools: post_trade → 'write:trades', adjust_cash → 'write:cash', etc.
• For what_if, add schema-level oneOf constraint to enforce exactly one of pct or price, rather than relying on prose description.
• For remove_news_source and similar operations, specify what happens if the resource doesn't exist (error message format, suggested alternatives).
• Add 'WHEN to use' guidance to tool descriptions. E.g., status: 'Call at start of decision or to check current P&L.' run_committee: 'Call to get a fresh 4-role vote on a symbol.'
• Consider refactoring tools 17-21 (get_history_data, analyze_multi_timeframe, etc.) to document output explicitly. Currently, descriptions only hint at structure (e.g., 'returns…最近 10 个交易日 + 起始/结束/最高/最低 4 个 anchor'). Register formal JSON Schema so LLMs know exact field names and types.