This server exhibits significant quality gaps across tool definitions. While schemas are present (using Zod validators), descriptions are minimal and often generic. Most tools lack actionable guidance for LLM selection. The 'query' tool is destructive and should be heavily restricted. Tool naming is reasonably clear but lacks consistency in verb-noun patterns. Parameter descriptions are sparse, and output schemas are not documented. Error handling exists but is minimal. Only 3 of 8 tools have descriptions that exceed 50 characters.

• Expand tool descriptions to 80-150 characters. Include WHAT (action), WHEN (selection criteria vs. similar tools), and PREVIEW of return structure. Example: 'Analyze campaign performance metrics over time. Returns impressions, clicks, spend, and ROAS by date. Call after campaign_id is known. Use vs. optimizeBudget: analysis is read-only; optimization recommends changes.'
• Document output schemas for all tools. Use structured format: 'Returns object with fields: campaign_id (string), metrics (array of {date (ISO 8601), impressions (int), clicks (int), spend (USD), roas (float)}), total_records (int).'
• Rename analyze tools to be more specific: 'get_campaign_metrics', 'get_adgroup_metrics', 'get_performance_trends' to eliminate LLM confusion.
• Add pagination parameters to listUsers: limit (1-100, default 20), offset (default 0). Document: 'Returns max 20 users per call. Use offset to paginate. Includes total_count field.'
• Add parameter constraints: createUser role should be enum (admin, analyst, viewer); email should match regex /^[^@]+@[^@]+\.[^@]+$/; password should require 8+ chars with hint in description.
• Extend getUser to accept natural identifiers: add user_email (string) and user_name (string) parameters as alternatives to id. Document: 'Pass one of: id (internal UUID), user_email, or user_name. Returns user with all three fields.'
• Improve error handling with recovery guidance. Example for getUser not found: 'User "john@example.com" not found. Try listUsers() to see available users, or createUser() to add them.'