Server exposes 7 read-only tools with clear naming (verb_noun pattern: get_*, list_, search_) and reasonable descriptions (avg ~120 chars). All tools have input schemas with type definitions and parameter descriptions. However, output schemas are not documented in the source, LLMs cannot predict return structure. Parameter descriptions lack format constraints (e.g., ISO date format for 'since'/'until' is mentioned in description but not formalized). No error handling guidance visible. Tools are well-composed (single responsibility) and idempotent (all READ_ONLY). Naming is consistent and action-oriented.

• Document output schemas for all 7 tools. For each, specify: field names, types (string, number, array, object), required vs optional, and nesting depth. Example: 'Returns {holdings: [{symbol: string, shares: number, cost_basis: number, current_price: number, unrealized_pnl: number, return_pct: number}], cash: number}'.
• Add JSON Schema format constraints to date parameters. Change 'since' and 'until' descriptions to include 'format: date (YYYY-MM-DD)' and add a regex pattern in the schema: '^\d{4}-\d{2}-\d{2}$'.
• Formalize the 'action' parameter in list_trades as an enum: {type: 'string', enum: ['BUY', 'SELL']}. This prevents hallucinated values and makes the tool self-documenting.
• Add error recovery guidance. For get_decision and get_debate, document: 'If run_id or date not found, returns {error: 'not_found', available_dates: [...]}. Call list_decisions to discover valid dates.'
• Clarify pagination behavior. Document: 'Returns up to `limit` results (default 20, max 100). If more results exist, response includes `has_more: true` and `next_cursor`. Use next_cursor in a follow-up call to fetch the next page.'