Server has 4 tools with complete input schemas and descriptions. Naming follows verb_noun pattern (abfuhrtermine, finde_traeger, traeger_details). Descriptions are present and contextual (avg ~120 chars), exceeding the 10-char minimum. However, parameter descriptions lack actionable constraints (no enums for abfallarten, no format specs for dates). Output schemas are not documented. Error handling is absent from visible code, no recovery guidance or categorization. Tool composition is sound (each does one thing), but descriptions could better explain when to use each tool vs. alternatives.

• Document output schema for each tool. Example: abfuhrtermine returns {traeger_id, traeger_name, termine: [{datum, abfallart, bemerkung}], portal_url}. This enables chaining to traeger_details and helps LLM extract dates.
• Add enum constraint to abfallarten parameter: ['Bio', 'Papier', 'Restmüll', 'Gelber Sack', 'Sperrm üll', ...]. Replace free-form string with validated options.
• Clarify date format in von/bis descriptions: 'ISO 8601 date string (YYYY-MM-DD). Default: today. Example: 2025-01-15'.
• Add error recovery guidance to tool descriptions. E.g. abfuhrtermine: 'If address is ambiguous, returns list of matching Entsorgungsträger, call traeger_details on each to disambiguate, then retry with traeger_id.'
• Expand tool descriptions with decision logic: 'Use abfuhrtermine for user-provided addresses. Use abfuhrtermine_fuer_traeger if you already know the carrier ID (from finde_traeger or prior context).'

Inferred effective spec: 2025-06-18+.

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