28 tools with basic schemas and descriptions, but significant quality gaps. All tools have descriptions (10-150 chars, mostly adequate) and input schemas with type definitions. However, parameter descriptions are sparse or generic ('Address data', 'Cart data'), output schemas are undocumented, and error handling is absent. No tool annotations (readOnlyHint/destructiveHint). Naming is mostly verb_noun (zones, cart_get, address_create) but some are ambiguous (home, category vs categories). No pagination guidance in descriptions despite tools accepting page/limit params. Risk classifications present but not integrated into tool metadata.

• Document output schemas for all 28 tools. For list tools (zones, categories, offers), specify: [{id, name, ...}], total_count, next_page. For detail tools (product, order_get), specify all returned fields with types.
• Expand parameter descriptions for address_create and address_update. Replace 'Address data' with: 'Object with required fields: street (string), city (string), zipCode (string), country (string). Optional: apartment, notes.'
• Add tool annotations to mcp-worker.ts tool registration. Mark READ_ONLY tools with readOnlyHint=true, DESTRUCTIVE tools with destructiveHint=true, idempotent tools with idempotentHint=true.
• Rename 'home' to 'get_home_content' or 'get_zone_home' to clarify the action. Rename 'category' to 'get_category_products' to distinguish from 'categories' (list all).
• Add error recovery hints to descriptions. E.g., coupon_apply: 'If coupon code is invalid, call coupons_list() to see available codes.' address_update: 'If address not found, call addresses_list() first.'

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

• Relies on Stateful initialize / Mcp-Session-Id (removed; protocol is stateless) - make each request self-contained