Four tools with basic verb-noun naming (get_, list_, search_). All have descriptions (10-50 chars, below baseline 194 chars). Input schemas present via Zod but minimal, only 1-2 params per tool, no enums or constraints. Output schemas not documented; responses are JSON strings, not structured objects. Error handling is generic ('Failed to fetch X') with no recovery guidance. No parameter descriptions beyond the tool description itself. Missing: pagination, output schema docs, actionable error messages, and per-parameter descriptions.

• Add per-parameter descriptions in tool registration. E.g. 'productId: The unique identifier of the product (string, required)' instead of relying on the tool description alone.
• Document output schemas explicitly. Define what fields each tool returns (e.g. getProductInfo returns {product: {id, name, category, price}, relatedOrders: [{id, productId, customerId, quantity, orderDate, status}]}).
• Implement pagination for listProducts and searchProducts. Add limit (default 20, max 100) and offset parameters; return total count and next_offset in response.
• Replace generic error handling with actionable messages. E.g. 'Product not found. Try searchProducts() to find a matching product by name or category.' Include error classification (retryable vs user-fixable).
• Expand tool descriptions to 100-200 chars. Explain WHEN to use each tool (e.g. 'Use getProductInfo for detailed product data including related orders; use listProducts to discover all available products').