Server has 6 tools with basic verb-noun naming (get_*, find_*) and descriptions present. However, descriptions are generic and lack actionable context for LLM selection. All tools accept single string parameters with minimal type information. No output schemas are documented, critical for agent planning. Parameter descriptions are trivial (e.g., 'Stock ticker symbol' with no format guidance). No error handling guidance, no pagination support despite tools returning lists, and no indication of which fields downstream tools need. Schemas are inferred from function signatures rather than explicitly declared.

• Document output schemas for all tools. Example: stock_profile returns {ticker: string, name: string, sector: string, price: float, market_cap: string}. Include all fields the agent might need for downstream calls.
• Enhance descriptions to 100-150 chars explaining WHAT, WHEN, and WHAT-RETURNS. Example: 'Get detailed stock profile (name, sector, price, market cap). Use this before price_history to understand the company. Returns structured object with all key metrics.'
• Add enum constraint to get_sector sector_name parameter: {type: 'string', enum: ['energy', 'basic-materials', 'technology', 'financial-services', 'healthcare', 'industrials', 'real-estate', 'utilities', 'consumer-defensive', 'consumer-cyclical']}
• Add pagination to stock_news and price_history: accept limit (1-100, default 20) and offset parameters. Return total_count and next_offset in response so agent can fetch more if needed.
• Add parameter format guidance: ticker_symbol description should state '2-5 uppercase letters (e.g., AAPL, MSFT)'. company_name should state 'Full or partial company name (e.g., Apple Inc, Microsoft)'. This prevents LLM from passing invalid values.

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

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