Three tools with reasonable naming (verb-first) and documented descriptions, but schemas lack critical parameter constraints, output documentation is missing, and error handling guidance is minimal. Tool names are clear but descriptions are short and lack WHEN/WHY context for LLM selection. Parameters have type definitions but are missing enums for constrained fields (format, quality). No documented output schemas visible in source. The server supports resources and logging, showing some production awareness, but tooling patterns are incompletely realized.

• Add enum constraints to 'format' and 'quality' parameters in enqueue_download schema. Example: {"format": {"type": "string", "enum": ["mp3", "flac", "aac", "opus"]}, "quality": {"type": "string", "enum": ["v0", "v2", "320", "160", "96", "256", "192", "lossless"]}}
• Expand tool descriptions to 150 - 250 characters each, adding WHEN context. Example for probe_url: 'Probe a media URL to detect the hosting provider and retrieve metadata (title, artist, duration, artwork). Call this first to validate URLs and gather metadata before enqueueing downloads.'
• Document output schemas for all three tools. For probe_url, specify: {"provider": string, "title": string, "artist": string, "duration": number (seconds), "artwork_url": string | null}. For get_job_status, document per-state outputs.
• Add error recovery guidance to probe_url: 'If the URL is unsupported or metadata cannot be retrieved, return a clear error message listing supported providers (YouTube, SoundCloud, Yandex Music).'
• Implement a dry-run parameter for enqueue_download (default false) or add a separate preview_download tool that shows what would be downloaded without committing.
• Document parameter relationships in enqueue_download description: 'quality values vary by format: mp3 supports v0/v2/320; opus supports 160/96; aac supports 256/192; flac is always lossless.'
• Add timeout and retry guidance to all tools. Example: 'If a download times out after 30 seconds, the tool will retry up to 3 times before failing.'
• Document what happens when a job_id in get_job_status does not exist (not found error, available alternatives, etc.).

Inferred effective spec: 2026-07-28+.

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