Two tools with basic Zod schemas and Chinese descriptions. Both tools have input schemas with type definitions (Zod), but descriptions are minimal (under 100 chars) and lack actionable context for LLM selection. Parameter descriptions exist but are terse (e.g., '快递公司名称或快递编码' = 'express company name or code'). No output schema documented. Error handling returns plain text without recovery guidance. Tool names lack English verb prefixes, making them opaque to English-speaking LLMs. No pagination, no structured output format specified, no tool annotations.

• Rename tools to English verb_noun format: 'query-express' → 'get_express_tracking', 'compare-price' → 'search_express_prices'. Start with action verbs (get, search, list, create) that LLMs recognize.
• Expand descriptions to 100-200 characters with WHEN/WHY context: 'Get real-time tracking status for a shipment. Use this when you have a tracking number and need current location, delivery status, or logistics history. Returns formatted tracking events with timestamps.'
• Document output schema explicitly. Define that responses contain 'tracking_number', 'carrier', 'status', 'events' (array of {timestamp, location, status_text}). Specify that price comparison returns array of {carrier_name, price, delivery_time, discount}.
• Add format constraints to parameters: phone as regex '^1[3-9]\d{9}$' (Chinese mobile), from/to as city names or postal codes with examples. Replace optional string defaults with enums where applicable (e.g., show: '0'|'1').
• Enhance error messages with recovery guidance: 'Invalid tracking number format. Expected 10-20 alphanumeric characters. Try search_express_carriers() to find the correct carrier code first.' Include available carriers in 'company not found' errors.

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

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry