The server defines 19 tools with explicit schemas and descriptions visible in server.py. Most tools follow verb_noun naming (arr_execute, arr_list_services, sonarr_search_series, etc.). However, critical quality gaps significantly limit production readiness: (1) Parameter descriptions are minimal or missing for most tools, e.g., sonarr_add_series accepts quality_profile_id and root_folder_path with only 1-2 word descriptions, no guidance on valid ranges or format; (2) Output schemas are completely undocumented, tool responses are never shown, forcing LLMs to infer result structure; (3) Error handling is absent from tool definitions, no guidance on what errors to expect, whether retryable, or how to recover; (4) Many parameters lack type constraints, quality_profile_id and series_id are integers but no min/max bounds; (5) Generic descriptions fail to convey prerequisites or dependencies, arr_execute's description lists examples but doesn't explain routing logic, failure modes, or when to use arr_explain_intent instead. The high-level intent router pattern (arr_execute + arr_explain_intent) is novel but reduces clarity for agents unfamiliar with natural-language routing. Per-tool analysis follows.

• Document output schemas for all 19 tools. For each tool, provide a JSON example or schema showing field names, types, and nested structure. At minimum, document 5-10 key fields returned by each.
• Expand parameter descriptions to 30-100 characters with actionable guidance. Example: 'quality_profile_id (integer, required): The Sonarr quality profile ID. Call sonarr_get_quality_profiles() first to discover available IDs. Common IDs: 1=HD, 2=4K. Range: 1-100.'
• Add error handling hints to all write tools (arr_execute, sonarr_add_series, radarr_add_movie, bazarr_download_subtitle, overseerr_request_media). Example: 'Returns 409 Conflict if series already exists. Returns 400 Bad Request if quality_profile_id is invalid, call sonarr_get_quality_profiles() to list valid IDs.'
• Define numeric constraints in parameter descriptions. Example: 'limit (integer, default=20): Number of results to return. Range: 1 - 100.'
• Add pagination parameters to result-returning tools. Introduce limit (default 20, max 100), offset (default 0), and document total_count in responses. Example: 'Call sonarr_get_series(limit=50) to retrieve up to 50 series; use offset=50 for the next page.'
• Clarify arr_execute vs service-specific tools. Add to arr_execute description: 'Use this for natural-language queries like add Breaking Bad, search The Matrix. For fine-grained control or when you have IDs, use service-specific tools like sonarr_search_series or sonarr_add_series directly.' Add to arr_explain_intent: 'Call this first to understand routing if unsure which service will handle your query.'

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

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