Server has 5 tools with explicit schemas and descriptions. All tools are properly registered via mcp-handler with Zod validation. Naming follows verb_noun convention (ping, search, create, get). Descriptions are present but brief (10-80 chars, below the 194-char baseline). Parameters have types and some constraints (e.g., z.number().positive(), z.string().url()), but descriptions for individual parameters are minimal or absent in the schema definitions. Output is JSON-stringified text, not structured. No error handling guidance, no pagination support, no idempotency markers. Security: Stripe/Shopify keys injected server-side (good), but no audit logging visible.

• Expand tool descriptions to 100-200 chars. Include WHAT the tool does, WHEN to use it, and what structure it returns. E.g., 'Search Shopify products by keyword. Returns up to 10 matching products with id, title, price. Use before creating checkout sessions.'
• Add explicit parameter descriptions in tool registration. Instead of relying on Zod constraints, add text: 'limit: Maximum products to return (1-100, default 10)'. LLMs cannot read JSON Schema, they need prose.
• Return structured objects instead of JSON-stringified text. Modify handlers to return { content: [{ type: 'text', text: JSON.stringify(...) }] } with a documented schema comment. Better: return typed objects and let mcp-handler serialize.
• Add error recovery guidance. Wrap external API calls with try-catch that returns actionable messages: 'Shopify API unavailable. Retry in 30s or check API status.' instead of raw errors.
• Implement pagination for shopify_search_products. Add 'offset' parameter and return { products: [...], total: N, hasMore: bool }. Document the 10-item default limit in the description.