Two tools with complete input schemas and descriptions, but descriptions are minimal (under 100 chars) and lack actionable context. Both tools are READ_ONLY and well-named with verb_noun pattern. No output schemas documented. Parameters have types and descriptions, meeting baseline requirements. Error handling present but generic. No tool annotations (readOnlyHint/destructiveHint). Schemas are properly structured JSON Schema with required fields declared.

• Add output schema documentation to both tools. Example for lookup_order: 'Returns {order_id: integer, status: string, carrier?: string, eta?: string}'. This enables LLMs to chain calls and extract fields.
• Expand tool descriptions to 100-150 chars explaining WHEN to use each. E.g. 'lookup_order: Retrieve order details by ID. Call this first to get carrier info, then use get_order_tracking for real-time status.' This guides multi-step planning.
• Add readOnlyHint: true to both tool definitions in the schema. This signals to LLMs that these calls are safe to retry and have no side effects.
• Enhance error messages with recovery guidance. Instead of 'Unknown tool: {name}', return 'Tool not found. Available tools: lookup_order, get_order_tracking'. For invalid order_id, return 'Order 999 not found. Verify the order ID is numeric and exists in the system.'
• Document parameter constraints in descriptions. For order_id, add '(positive integer, typically 1000-9999)'. For tracking_number, specify format expectations like 'FedEx/UPS/DHL tracking code (alphanumeric, 10-30 chars)'.