Two tools with basic schemas and German descriptions. Naming follows verb conventions (search_, get_). Descriptions are present but brief (10-15 chars core action). Input schemas are explicit and typed with enums on get_orders, but output schemas are not documented in source. Error handling exists (required param validation) but lacks recovery guidance. Tool annotations (OpenWorldHintAnnotation) are present, which is positive. No pagination documented despite potential for order lists to grow large. Parameter descriptions are adequate but could better explain context (e.g., what 'kundenNummer' represents beyond 'customer number in CRM').

• Document the output schema for both tools. Add a 'Returns' section to each tool description or store schema metadata accessible to clients. Example: 'Returns: {customer_id: string, company_name: string, contact_person: {firstname, lastname, email}, company_address: {street, postcode, city, country}}'.
• Expand tool descriptions to 50-150 characters explaining business context. Example: 'Search for a customer in the CRM by customer number. Returns company name, address, and primary contact. Use this to retrieve customer details before calling get_orders.'
• Add pagination to get_orders: include 'limit' parameter (default 20, max 100) and return 'total_count' and 'has_more' fields. Document in description: 'Returns up to 20 orders. Use limit and offset for pagination.'
• Improve error messages with actionable recovery hints. Example: Instead of 'kundenNummer is required', return 'kundenNummer (customer number) is required. If unknown, call search_customer() with company name or contact email first.'
• For get_orders, add constraint documentation to status parameter description: 'Filter by order status. Valid values: waiting (not yet processed), offen (open/in progress), verschickt (shipped). Default: offen.' This helps LLMs avoid hallucinating invalid status values.
• Replace mock data with real CRM/ERP backend calls. Add logging or metrics to track tool invocations and failures in production.
• Consider adding a 'get_customer_detail' or 'get_customer_info' tool that enriches search results with order history, payment terms, and contact history in a single call, reducing multi-step agent planning.

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry