22 tools with consistent naming (verb_noun pattern) and Chinese descriptions. However, critical gaps: (1) ALL parameter descriptions are in Chinese, making them inaccessible to English-speaking LLMs and violating the pattern:tool-description baseline of 100% A+ tools having English descriptions; (2) NO input schemas are visible in the source code, tool definitions use mcp.WithString() but no explicit JSON Schema with type/description pairs; (3) Output schemas completely undocumented, no indication of what fields are returned; (4) Error handling absent, toolResult() returns raw errors without recovery guidance; (5) No pagination support despite tools like list_accounts, list_campaigns, list_ads that likely return multiple items. Tool names are clear (list_*, get_*, update_*, delete_*) but parameter constraints (enums, ranges) are missing entirely.

• Translate all parameter descriptions and tool descriptions to English. Use clear, LLM-optimized English (50-200 chars per description) following the pattern:tool-description baseline.
• Document explicit JSON Schema for all tools with type, description, and constraints (enums, min/max, patterns) for every parameter. Make schemas visible in code or generated documentation.
• Add output schema documentation for each tool. Specify what fields are returned, their types, and which fields are needed for downstream tool calls (e.g., if update_campaign_status needs campaign_id, list_campaigns must return campaign_id).
• Implement error handling with recovery guidance. Replace raw errors with actionable messages: 'Invalid status: got "pending", must be one of: enable, disable, delete' and 'User not found. Try list_accounts() first.'
• Add pagination to list_* tools: accept limit (1-100, default 20) and offset/cursor parameters; return total_count and next_cursor in responses to enable multi-page iteration.