Server has 7 tools with explicit Zod schemas and descriptions. All tools are READ_ONLY except addCustomerTags (WRITE). Naming follows verb_noun pattern (find, list, get, add). However, descriptions are minimal (10-50 chars), parameter descriptions lack detail on constraints/formats, and output schemas are not documented. Error handling exists but is generic. No tool annotations (readOnlyHint/destructiveHint). Schemas are present but sparse, many parameters lack constraint documentation (e.g., limit ranges, enum values for sortKey are defined but not explained in description).

• Expand tool descriptions to 100-200 chars. Example: 'findProducts' → 'Search Shopify products by title or retrieve all products. Returns product details including variants, prices, and SKUs. Use this to discover products before adding to orders or checking inventory.'
• Document output schemas explicitly. Add a 'Returns' section to each tool description listing fields (e.g., 'Returns: product_id, title, variants[], price, sku'). Consider returning structured JSON instead of formatted text.
• Add min/max bounds to numeric parameters in descriptions. E.g., 'limit: Maximum number of products to return (1 - 250, default 20)'. Add enum descriptions: 'sortKey: Field to sort by, PROCESSED_AT (fulfillment date), TOTAL_PRICE (order value), CREATED_AT (order creation), etc.'
• Implement tool annotations. Mark addCustomerTags with destructiveHint=true. Mark all READ_ONLY tools with readOnlyHint=true. This enables agents to reason about side effects.
• Enhance error handling with categorization. Return structured errors: {code: 'NOT_FOUND', message: 'Product not found', retryable: false, suggestion: 'Try search_products() with a partial title'}. Guide LLM recovery.