Two tools with basic schemas and descriptions, but significant gaps in parameter documentation, output schema clarity, and error handling guidance. Tool names follow verb_noun convention (get_*), which is good. However, descriptions are minimal (34-45 chars, below the 50-200 char LLM-optimized baseline), and parameter descriptions lack actionable constraints. No output schema documented. Error handling returns plain text without recovery guidance. The server exposes API keys via environment variables (correct), but tool implementations lack input validation and return unstructured text responses instead of structured JSON.

• Expand tool descriptions to 80-150 chars. Example: 'get-hs-stock-data: Fetch real-time Shanghai/Shenzhen stock prices and index data. Provide either a stock code (sh601009, sz000001) or index type (0=SSE Composite, 1=SZSE Component). Returns current price, change %, open/high/low, volume, and timestamp.'
• Add explicit constraints to parameter descriptions. For 'type' enum, write: 'Index type: 0 = SSE Composite Index, 1 = SZSE Component Index. Mutually exclusive with gid parameter.'
• Refactor tools to return structured JSON instead of plain text. Example output: {"name": "...", "currentPrice": 123.45, "change": 0.5, "changePercent": 0.41, "open": 123.0, "high": 124.0, "low": 122.5, "volume": 1000000, "timestamp": "2024-01-15T10:30:00Z"}
• Implement error categorization. Return {"error": "User not found", "category": "user_fixable", "suggestion": "Try search_users() with a partial name or verify the stock code format (e.g., sh601009)."}
• Add input validation with actionable error messages. Example: 'Invalid page number: got "abc", must be a positive integer (1-100). Invalid type: got "5", must be one of: 1, 2, 3 (items per page: 20, 40, 60).'