Server has 9 tools with explicit Zod schemas and descriptions. Naming follows verb_noun pattern (get-, create-, tag-). However, descriptions are minimal (10-50 chars, well below the 194-char baseline), lack context on WHEN to use each tool, and omit recovery guidance. Schemas are present but sparse, many parameters lack detailed constraints. Output formatting is ad-hoc (JSON.stringify or custom formatProduct). No pagination metadata (total count, next_cursor) returned. Error handling is generic ('Failed to retrieve X') with no recovery hints. Missing tool annotations (readOnlyHint, destructiveHint). Overall: functional but below production baseline.

• Expand tool descriptions to 100-200 chars. Include WHAT the tool does, WHEN to use it (vs similar tools), and any prerequisites. Example: 'Get all products or search by title. Use this for broad product discovery; use get-products-by-collection for category-specific results. Returns up to [limit] products with variants and pricing.'
• Add tool annotations: mark get-* tools with readOnlyHint=true; mark tag-customer and create-discount with destructiveHint=true and idempotentHint=false (or true if idempotent).
• Enhance error handling: return structured errors with category (retryable|user_fixable|fatal), invalid value, and constraint. Example: 'Invalid limit: got 1000, must be 1-100. Retryable: false.'
• Document output schemas explicitly. Define fields returned by each tool (e.g., product: {id, title, description, variants: [{id, title, price, sku}]}). Return structured objects, not formatted text.
• Improve pagination: return total_count and next_cursor in paginated responses. Cap results at 20-50 items by default. Document limits in tool descriptions.