Server defines 6 tools with complete input schemas and descriptions in Chinese. Naming follows verb_noun pattern (create_order, get_order, list_orders, set_address). However, descriptions lack English translations and are terse (avg ~80 chars). Parameter descriptions are minimal, most lack format/range guidance. No output schemas documented. Error handling returns raw API errors without recovery guidance. No tool annotations (readOnlyHint/destructiveHint). Missing idempotency guidance for write operations. Schemas are present but sparse on constraints (e.g., amount_usdt range stated in description but not as JSON Schema min/max).

• Add English descriptions to all tools and parameters. Minimum 50 chars, maximum 200 chars. Include WHAT the tool does, WHEN to use it, and any prerequisites. E.g., 'Create a USDT(BSC) payment order. Merchant must be active and have a BSC address bound via set_address(). Returns order_no, amount, address, and checkout link.'
• Document output schemas for all tools. Define the structure of create_order response (order_no: string, amount_usdt: number, bsc_address: string, checkout_url: string, etc.). This enables agents to extract and chain results.
• Add JSON Schema constraints: amount_usdt with minExclusive: 0, maximum: 1000000; address with pattern: '^0x[0-9a-fA-F]{40}$'; callback_url with format: 'uri'. Remove format hints from descriptions and move to schema.
• Add tool annotations: mark get_order, check_order_public, list_orders, merchant_me with readOnlyHint: true; mark create_order, set_address with destructiveHint: true (or idempotentHint if retryable). This guides agent planning.
• Enhance error messages with recovery guidance. E.g., if create_order fails with 'Merchant not active', return 'Merchant not active. Activate via the dashboard or contact support.' If 'No address bound', return 'No BSC address bound. Call set_address() first.'