Server has 10 tools with consistent naming (verb_noun pattern: get_*) and basic schemas. All tools have descriptions and input parameters with types. However, descriptions are generic and lack LLM-optimization guidance. Output schemas are not documented, tools return JSON strings rather than structured objects. No error handling guidance, no parameter constraints (enums), and no indication of what fields downstream tools should expect. Parameter descriptions are minimal (e.g., 'Ticker symbol of the company (e.g. AAPL, GOOGL)' repeated across tools). Tools 8 and 9 (get_crypto_prices and get_historical_crypto_prices) appear to be duplicates with identical signatures, violating single-responsibility principle.

• Document output schemas for all tools. Specify the structure of returned JSON (e.g., income_statements returns array of {ticker, period, date, revenue, net_income, ...}). This enables LLMs to plan downstream operations.
• Convert parameter descriptions to use JSON Schema enums. Replace 'Period of the income statement (e.g. annual, quarterly, ttm)' with enum: ['annual', 'quarterly', 'ttm']. This prevents hallucinated values and is machine-parseable.
• Merge get_crypto_prices and get_historical_crypto_prices into a single tool. Both fetch historical prices; the duplicate creates confusion. Consolidate under get_historical_crypto_prices and remove get_crypto_prices.
• Add actionable error messages with recovery guidance. Instead of 'Unable to fetch income statements or no income statements found', return 'No income statements found for ticker INVALID. Verify ticker is valid (e.g., AAPL, GOOGL) using a financial data source.'
• Add limit and pagination parameters to tools returning lists (get_available_crypto_tickers, get_company_news). Document max results in descriptions and return a total_count or next_cursor for large result sets.

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry