sonarr_add_series

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

Annotations declare readOnlyHint=false and destructiveHint=false, but the description adds no behavioral context beyond the primary action. It fails to disclose potential side effects such as searchForMissingEpisodes defaulting to true (which may trigger downloads) or that the series must not already exist.

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, clear sentence that immediately conveys the tool's purpose without any wasted words. It is perfectly sized for the information it provides.

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?

This tool has 8 parameters and no output schema, yet the description is extremely brief. It does not explain expected behaviors like auto-detection of rootFolderPath/qualityProfileId, or what the return value indicates on success. Given the complexity and side-effect potential, the description is insufficient.

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?

The schema already documents all 8 parameters with descriptions, and context signals show 100% coverage. The description adds little beyond highlighting TVDB ID as the key identifier, so it does not meaningfully enhance parameter understanding. Baseline 3 is appropriate.

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), the resource (a new series to Sonarr), and the key identifier (by TVDB ID). It distinguishes this tool from siblings like sonarr_search or sonarr_get_series by focusing on the creation use case.

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 gives no explicit guidance on when to use this tool versus alternatives, nor does it mention prerequisites or exclusions. It is implied that this is for adding new series, but there's no mention of checking existing series or using related tools like sonarr_get_profiles to obtain required IDs.

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