Sonarr: Add Series

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Discloses internal calls (/series/lookup then POST /series) and the return type (SeriesResource). Reveals that server-side default for search_for_missing_episodes is true, which may cause immediate indexer hits. Adds significant context beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Compact yet comprehensive paragraph. Every sentence contributes: purpose, internal workflow, return, and a crucial behavioral note. No verbosity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers prerequisites, internal process, return type, and a key default behavior pitfall. Despite no output schema, the description provides enough context for correct usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All 7 parameters are described in the schema (100% coverage). The description adds workflow context: tvdb_id from lookup, quality_profile_id from list, root_folder_path from list. Also explains the behavioral implication of search_for_missing_episodes default.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states the action (Add a new series), the resource (series), and the identifier (TVDB id). Distinguishes from sibling tools like sonarr_edit_series by specifying 'add' versus 'edit'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly prescribes a workflow: look up series first, then get quality profile and root folder. Also notes a behavioral nuance about search_for_missing_episodes default, guiding when to override.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.