X-Cart MCP has 16 tools with consistent naming (verb_noun pattern) and complete input schemas. Descriptions are present but generic, most lack context on WHEN to use the tool or what happens on failure. Parameter descriptions are minimal (5-15 chars typical). No output schemas documented. Error handling is absent. Tool composition is reasonable (single responsibility), but missing idempotency hints and recovery guidance. Naming is clear (asap_categories_list, brand_update, order_search) but descriptions read like API docs, not LLM prompts.

• Document output schemas for all tools. E.g., asap_categories_list should specify: returns {categories: [{id, name, mapped, parentId, ...}], total, hasMore}. This enables LLMs to chain tools correctly.
• Expand parameter descriptions to 50-100 chars with context. E.g., 'Filter by mapped or unmapped status' → 'Filter by mapping status: mapped (ASAP category linked to X-Cart) or unmapped (no X-Cart link yet). Helps identify categories needing manual review.'
• Add error recovery guidance. E.g., order_update_status: 'If order not found, call order_search first. If status code invalid, must be one of: Q (Queued), A (Authorized), PP (Partially Paid), P (Paid), D (Declined), C (Cancelled), R (Refunded).'
• Implement dry-run or confirmation for destructive ops. asap_auto_map should return proposed mappings first (apply=false default), then require explicit apply=true. asap_category_unmap should warn: 'This removes the mapping permanently. Call asap_categories_list to verify before unmapping.'
• Add idempotency hints to tool descriptions. E.g., category_assign_product: 'Idempotent, calling twice with same product_id and category_id is safe; product will be assigned once.' This guides agent retry logic.