sonarr_bulk_delete_series

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

With no annotations provided, the description carries the full burden. It explicitly warns that setting deleteFiles to true is destructive and irreversible, emphasizing the key risk. It does not disclose other side effects (e.g., whether the series record itself is removed or any auth requirements), but it addresses the primary hazard clearly enough to merit a 4.

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 two sentences: the first states the purpose directly, and the second delivers a critical warning. Both earn their place with no redundant filler, making it highly concise and front-loaded.

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?

For a delete tool with no output schema and no annotations, the description covers the most important context: the destructive nature of deleteFiles. It omits details about the addImportListExclusion parameter's effect, but that is documented in the schema. Overall it is sufficiently complete given the schema richness, but could have briefly mentioned the non-destructive default.

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% for all three parameters, each with clear descriptions (e.g., deleteFiles marked 'IRREVERSIBLE'). The description adds a warning that duplicates the schema's own note, so it provides little additional semantic value beyond what the schema already conveys. 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 tool's function: 'Bulk delete multiple series from Sonarr.' It uses a specific verb ('delete'), resource ('series'), and scope ('bulk multiple'), which distinguishes it from the sibling tool 'sonarr_delete_series' that presumably targets a single series.

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 phrase 'Bulk delete multiple series' indicates this tool is for deleting multiple series at once, implying it should be used instead of the single-series delete sibling for batch operations. However, it does not explicitly name alternatives or state when NOT to use it, so it falls short of a 5.

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