sonarr_delete_series

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

The description repeats the destructiveHint annotation with 'DESTRUCTIVE: this deletes data' but adds no new behavioral context. It does not disclose what exactly gets deleted (e.g., series metadata vs. files) or any side effects, so it offers little beyond the annotation.

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 very short and front-loaded with the core action. However, the redundant warning about destructiveness adds no value, and the extreme brevity sacrifices necessary details.

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?

The description is incomplete for a delete tool with three parameters. It lacks any mention of parameter behavior, single-series scope, or distinction from bulk delete. The output schema exists, but that does not compensate for missing parameter and usage context.

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 0%, and the description provides no explanation of the parameters (id, delete_files, add_import_list_exclusion). This is a significant gap, as the meaning and implications of delete_files and add_import_list_exclusion are critical for correct usage.

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 tool deletes a series, which is a specific verb+resource. However, it does not explicitly differentiate from sibling tools like sonarr_bulk_delete_series, so it lacks explicit sibling differentiation.

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?

There is no guidance on when to use this tool vs alternatives. It does not mention that this is for a single series, nor does it point to bulk deletion for multiple series. No when-to-use or exclusions are given.

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