sonarr_add_series

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

With no annotations, the description carries full burden, but it only says 'Add a new series' without disclosing key behavioral traits like what happens on duplicate, whether searches are triggered, or any side effects. The schema implies defaults but the description does not summarize them.

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?

The description is a single concise sentence that front-loads the verb and resource. It is efficient, though it could include critical behavioral context without becoming verbose.

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?

Given 8 parameters, no output schema, and no annotations, the description is too brief. It omits important context like default behavior for optional parameters (e.g., monitored defaults to true) and the expected outcome (e.g., returns created series).

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?

Schema description coverage is 100%, so baseline is 3. The description adds no extra meaning beyond mentioning TVDB ID. It does not compensate by explaining how parameters interact (e.g., monitorType vs searchForMissingEpisodes).

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?

The description clearly states the action (add), resource (series), target system (Sonarr), and key identifier (TVDB ID). It effectively distinguishes from sibling tools like sonarr_get_series (get vs add) and radarr_add_movie (series vs movie).

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?

The description provides no guidance on when to use this tool versus alternatives, such as finding the series first via sonarr_search, or how to handle existing series. No explicit when-not or contextual usage advice is given.

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