Three tools with complete Zod schemas and descriptions in Russian. All tools are READ_ONLY and properly named with verb_noun pattern (get_orders, get_products, get_order). Schemas include proper type constraints (enums, min/max bounds). However, descriptions are minimal (10-20 chars in English translation), parameter descriptions lack context about when to use each tool, and output schemas are not documented. Error handling is basic (404 returns 'not found' text). No tool annotations (readOnlyHint, idempotentHint) despite all being read-only. Pagination is implemented but not clearly explained in descriptions.

• Expand tool descriptions to 100-150 chars. Example: 'get_orders: Retrieve a paginated list of Kaspi orders filtered by status (NEW, COMPLETED, etc.) and creation date range. Returns order ID, code, total price, status, customer name/phone, and delivery address. Use this to list orders; use get_order for detailed info on a single order.'
• Document output schemas in tool descriptions or as a separate schema field. Specify that get_orders returns an array of {id, код, сумма, статус, состояние, оплата, доставка, дата, клиент, адрес} and get_order returns a single object with the same structure plus nested customer and address details.
• Add readOnlyHint=true to all three tools in server.tool() registration to signal idempotency and retry-safety to agents.
• Enhance error handling: when get_order returns 404, include 'Try get_orders() to search for the order by status or date range.' When API times out, suggest retrying with a smaller page_size.
• Clarify pagination in get_orders and get_products descriptions: 'Results are paginated. If fewer items are returned than page_size, you have reached the end. Use page_number to iterate through results.'