Server has 12 tools with complete input schemas and descriptions. Naming follows verb_noun convention (search_products, add_to_cart, get_delivery_slots). However, descriptions are generic and lack LLM-optimized guidance on WHEN to use each tool vs. alternatives. Parameters lack enums where appropriate (e.g., category should be constrained). No output schemas documented. Error handling is minimal, no recovery guidance or actionable error messages. Missing parameter descriptions for get_product_details (url/product_id are ambiguous, which is required?). Checkout tool lacks confirmation pattern despite IRREVERSIBLE risk. Overall: functional but below production baseline.

• Add enum constraint to search_products 'category' parameter: {"enum": ["produce", "dairy", "meat", "bakery", "frozen", "pantry", "beverages", "prepared"]}. Update description: 'Category filter (required if narrowing results; valid values: produce, dairy, meat, bakery, frozen, pantry, beverages, prepared).'
• Fix get_product_details: clarify which parameter is required. Either make one required and the other optional, or document: 'Provide either url OR product_id. If both provided, url takes precedence.' Add descriptions: url: 'Full Whole Foods/Amazon product URL (e.g., https://www.wholefoodsmarket.com/product/...). Takes precedence over product_id.' product_id: 'Product ASIN or item ID (used if url not provided).'
• Add output schema documentation to all tools. Example for search_products: 'Returns {"products": [{"product_id": string, "name": string, "price": number, "url": string, "category": string}], "total": number, "limit": number}'. This enables LLM to extract product_id for add_to_cart calls.
• Enhance checkout description to include confirmation pattern: 'Proceed to checkout. Set confirm=false (default) to preview order without placing it. Set confirm=true only after user explicitly approves. Returns order summary and delivery options.' Add error handling: 'If confirm=true and order fails, returns specific reason (e.g., "Out of stock: item X", "Delivery unavailable for ZIP code") with recovery suggestions.'
• Add error handling to login tool: 'On failure, returns one of: {"error": "invalid_credentials", "message": "Email or password incorrect. Verify credentials and retry."} or {"error": "browser_timeout", "message": "Login took too long. Check internet connection and retry with headless=false to debug."} This guides LLM recovery.