Liquidus exposes 7 tools with basic descriptions and minimal parameter documentation. Tool names follow verb_noun convention (get_product, search_products, create_order, add_line_item), which is good. However, descriptions are terse (10-50 chars), parameter descriptions are sparse or missing entirely, and input schemas lack type information beyond basic string/integer declarations. No output schemas are documented. Error handling is absent, no guidance on retryability, user-fixable vs fatal errors, or recovery paths. The mock server (mocks/msw/server.mjs) shows HTTP handlers but the actual MCP server implementation is not visible in the provided source, making it impossible to verify tool registration, schema completeness, or error responses. Tools like add_line_item and create_order perform state-modifying operations but lack any confirmation or dry-run pattern.

• Expand tool descriptions to 100-200 characters. Include WHAT the tool does, WHEN to use it, and WHAT it returns. Example: 'Retrieve a single product by ID from the Solidus catalog. Returns product name, description, price, SKU, and available variants. Use this after search_products() to get full details.'
• Add parameter descriptions for all inputs. For 'token', explain: 'X-Spree-Order-Token header value from a previous create_order() or get_current_order() call. If omitted, a fresh cart is created.' For 'quantity', add: 'Number of units to add (1-999, defaults to 1).'
• Document output schemas for each tool. Show the JSON structure with field names, types, and meanings. Example for create_order: '{"id": number, "number": string, "token": string, "state": "cart"|"completed", "line_items": [...], "total": string}'
• Add error handling guidance. For get_product with invalid ID, return: 'Product not found. Try search_products() to find the correct ID.' For add_line_item with invalid token, return: 'Cart session expired. Call create_order() to start a new session.'
• Implement confirmation or dry-run for state-modifying tools. Before create_order or add_line_item, offer a preview of the action and require explicit confirmation. This prevents accidental duplicates and aligns with pattern:confirmation-request.