Six tools with complete schemas and descriptions in German. All tools are READ_ONLY with proper input schemas including type definitions and parameter descriptions. Tool names follow verb_noun pattern (epl_search_*, epl_list_*, epl_server_info, epl_rechtskontext). Descriptions are substantive (100-200 chars) and explain what each tool does. However, descriptions lack explicit guidance on WHEN to use each tool vs. alternatives, and error handling/recovery paths are not documented in tool definitions. Output schemas are not formally documented in the tool definitions themselves. Tool annotations present (readOnlyHint via ToolAnnotations) but not visible in provided schema snippets.

• Add formal output schema documentation to each tool definition. Example: 'Returns array of objects with fields: registration_number (string), trade_name (string), active_ingredient (string), dosage (string), form (string), approval_status (enum: approved|conditional|withdrawn).'
• Enhance search tool descriptions with decision guidance: 'Use epl_search_sl for medications covered by mandatory health insurance (KVG Art. 52). Use epl_search_ggsl for congenital defect medications (IVG). Use epl_search_migel for medical devices and aids (KLV Art. 20).'
• Document error scenarios and recovery paths: 'If no results found, try broader search terms or check epl_list_sources for data freshness. If API timeout occurs, retry after 5 seconds.'
• Rename epl_server_info → get_server_capabilities and epl_list_sources → list_data_sources for clearer action semantics.
• Add pagination guidance to search tools: 'Results are limited to 100 items. Use limit parameter to control page size. To fetch all results, iterate with offset or implement client-side pagination based on result count.'

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

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