Three tools with clear verb-noun naming (get_order_status, list_customer_orders, check_inventory) and solid descriptions (avg 95 chars, all >20 chars). Input schemas present with type definitions and parameter descriptions. However, output schemas are NOT documented, the code shows GraphQL queries and response processing, but no formal schema definitions are visible in the tool registration. Parameter descriptions are adequate but lack format constraints (e.g., email regex, order number format). No error handling guidance in descriptions. No tool annotations (readOnlyHint, etc.). Composition is sound: three independent, single-purpose tools with no overlapping responsibilities.

• Document output schemas for all three tools. For get_order_status, specify: {found: bool, order_number: string, placed_at: ISO8601, cancelled: bool, fulfillment_status: string, financial_status: string, total: string, items: [{title, quantity}], tracking: [{number, carrier, url}]}. Similar for list_customer_orders and check_inventory.
• Add format constraints to parameter descriptions. E.g., 'order_number: The customer's order number (digits only, 1-10 digits, e.g., #1001).' 'email: Valid email address (RFC 5322 format).' 'product_query: Free-text search (max 100 chars, alphanumeric + hyphens).'
• Add tool annotations to the MCP tool registration. Mark all three tools with readOnlyHint=true to signal they are safe to cache and retry.
• Enhance error descriptions. E.g., 'If order not found, the email may not match the order. Ask the user to verify the email address or try a different order number.' For inventory, 'If no products match, try a broader search term (e.g., "jacket" instead of "rain jacket").'
• Add pagination to list_customer_orders. Accept optional limit (1-50, default 10) and offset parameters. Return total_count and has_more flag so agents can fetch older orders if needed.