Server provides 6 tools with complete input schemas and descriptions. Naming follows verb_noun pattern (GetCategories, GetRegions, etc.). However, descriptions lack LLM-optimized guidance on WHEN to use each tool vs alternatives, and parameter descriptions are minimal (avg 40 chars vs baseline 72). Output schemas are not documented, LLMs cannot predict response structure. GetProducts has a confusing 'keyword' parameter marked optional when the description says 'must be filtered by category ID', creating ambiguity. GetTodayTradeList is complex (16 params) but lacks guidance on mutually exclusive or dependent parameters. No error handling documentation visible. Tool descriptions average 150 chars (within baseline 194), but lack dependency hints and recovery guidance.

• Document output schemas for all tools. E.g., 'Returns array of {id: int, name: string, code?: string}'. Include this in tool descriptions or a separate schema reference.
• Clarify GetProducts: if categoryId is mandatory, mark it as required (not optional) and remove the optional keyword parameter, or explain when keyword alone is sufficient.
• Add dependency documentation to GetTodayTradeList: 'regionIds and districtId are mutually exclusive. Pass one or the other, not both. If both are provided, regionIds takes precedence.'
• Add error recovery hints to all tools. E.g., 'If no results found, try a shorter keyword or check spelling. For Russian categories, use Cyrillic characters.'
• Expand parameter descriptions to 60-100 chars with format/range info. E.g., 'Search keyword (Russian Cyrillic, 1-50 chars, case-insensitive substring match).'