Server has 5 tools with complete schemas and descriptions in Russian. All tools follow verb_noun naming (search_*, get_*) and are READ_ONLY. However, descriptions are minimal (10-20 chars), parameter descriptions lack context about constraints and formats, and output schemas are not documented. No error handling guidance, no pagination metadata in responses, and no tool annotations. Schemas are present but sparse, parameters lack examples of valid ranges and formats beyond basic type info.

• Expand tool descriptions to 100-200 chars. Example: 'search_vacancies' → 'Search job vacancies on SuperJob by keyword, city, and salary range. Returns up to 100 results per page. Use get_towns() to find valid city IDs. Requires SUPERJOB_SECRET_KEY env var.'
• Add constraint descriptions to all parameters. Example: 'town' → 'City ID (integer). Valid IDs: 4=Moscow, 14=St. Petersburg. Call get_towns() to discover all valid IDs. Required for accurate search results.'
• Document output schemas for each tool. Example for search_vacancies: 'Returns {objects: [{id, profession, company, town, payment_from, payment_to, date_published}], total: number, more: boolean}'.
• Add error handling guidance in tool descriptions. Example: 'If town ID is invalid, error message will suggest calling get_towns(keyword=...) to find the correct ID.'
• Implement structured response formatting. Instead of JSON.stringify(result), parse the API response and return only relevant fields (id, title, salary, location) with pagination metadata (total_count, has_more).