Two tools with minimal schema documentation and vague descriptions. get_portfolio has a basic optional parameter but lacks output schema documentation. get_context has an optional query parameter but no schema details. Both descriptions are generic and lack specificity about return structure, error cases, or when to use each tool. No parameter type constraints (enums, ranges). No documented output schemas. No error handling guidance. Naming is acceptable (verb_noun pattern) but descriptions fall short of the 50-200 char LLM-optimized baseline.

• Add explicit output schemas for both tools. Document that get_portfolio returns {holdings: [{asset, amount, usd_value, allocation_pct}], total_usd_value, last_updated}. Document get_context returns {profile, strategy_notes, portfolio_snapshot, trading_patterns, fund_flows}.
• Enhance parameter descriptions with type and format constraints. For 'asset': 'Optional: filter by specific asset symbol (e.g., BTC, ETH, USDC). If omitted, returns all holdings.' For 'query': 'Optional: natural language question or topic (max 500 chars). If omitted, returns full profile.'
• Clarify when to use each tool. Add to get_portfolio: 'Use this for quick portfolio snapshot and allocation percentages.' Add to get_context: 'Use this for comprehensive investor profile, strategy notes, and trading pattern analysis.'
• Add error handling guidance. E.g., 'If no exchanges are connected, returns empty holdings array. If query is malformed, returns error with suggestion to rephrase.'
• Document pagination/limits if applicable. If either tool can return large result sets, add limit and offset parameters with documented defaults (e.g., limit=50, max=500).