The server provides 3 tools with basic functional definitions but significant quality gaps. All tools have descriptions and input schemas present, but descriptions are minimal (10-30 chars) and lack actionable guidance. Parameter descriptions exist but are sparse. No output schemas are documented. Error handling returns dictionary responses with error keys but provides no recovery guidance or categorization. The codebase shows good internal practices (rate limiting, caching, input validation) but these are not surfaced in the tool definitions where LLMs need them. Tools follow verb_noun naming (get_*) which is correct. However, the definitions lack the depth needed for reliable LLM selection and execution.

• Expand tool descriptions to 50-200 characters. For get_stock_price: 'Fetch the current market price, previous close, day high/low, volume, market cap, PE ratio, and 52-week range for a stock symbol. Use this to answer price-based questions or monitor intraday movements. Returns N/A for data not available for the symbol.'
• Document output schemas explicitly. Add a 'returns' section to each tool docstring listing all output fields, types, and what they mean. E.g., for get_stock_price: {'symbol': str, 'current_price': float, 'previous_close': float, ...}
• Replace example values in parameter descriptions with formal constraints. Change 'Stock ticker symbol (e.g., AAPL, GOOGL)' to 'Stock ticker symbol: 1-5 uppercase letters, numbers, periods, hyphens, carets, or equals signs (e.g., BRK.B, BF-A)' and encode the constraint as a JSON Schema pattern or enum.
• Add error recovery guidance. When validation fails, return: {'error': 'Invalid period: "6mo". Must be one of: 1d, 5d, 1mo, 3mo, 6mo, 1y, 2y, 5y, 10y, ytd, max'} instead of a generic 'Invalid period' message.
• Declare period, interval, and sort_by as enum types in JSON Schema. For get_historical_data, period should be: {'type': 'string', 'enum': ['1d', '5d', '1mo', '3mo', '6mo', '1y', '2y', '5y', '10y', 'ytd', 'max'], 'description': '...'}
• Add per-tool semantic tags (tool annotations) to clarify safety and idempotency. For all three tools, mark readOnlyHint=true since they do not mutate state.
• Document pagination and limits. get_options_chain accepts a limit parameter (default 20), explain why results are capped (context window), what happens if more exist (truncated), and how to retrieve the next page if needed.