Two tools with basic verb-noun naming (getLatestStockPrices, getHistoricalStockPrices) and minimal descriptions. Both descriptions are under 30 characters, failing the 10-1024 character guideline. Input schemas are present with typed parameters (string, integer) but lack depth. No output schema documentation visible. No error handling guidance, recovery paths, or parameter constraints (e.g., valid company names, day ranges). Tool annotations (readOnlyHint) are declared in metadata but not reflected in schema. No pagination support despite getHistoricalStockPrices returning lists. Descriptions do not explain WHEN to use each tool or what distinguishes them.

• Expand tool descriptions to 50-150 characters. Example: 'getLatestStockPrices: Fetch the most recent stock price for a company (updated every minute). Returns current price as a float. Use this for real-time price checks; use getHistoricalStockPrices for trend analysis.'
• Add parameter constraints: company as enum or with validation pattern; days with min=1, max=365. Document in parameter descriptions: 'days: Number of historical days to retrieve (1-365, default 30).'
• Document output schemas in tool metadata. For getHistoricalStockPrices, specify: returns List<{company: string, close: float, datetime: string}>. For getLatestStockPrices, specify: returns {price: float}.
• Add a discovery tool (list_supported_companies or search_companies) to help LLMs find valid company names without guessing.
• Implement error handling that returns structured errors with recovery hints. Example: '{error: "Company not found", suggestion: "Try search_companies(\"apple\") or use ticker symbol AAPL", retryable: false}'.

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

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