sonarr_bulk_delete_series

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

The description only repeats what the annotations already signal (destructiveHint=true) by stating 'DESTRUCTIVE: this deletes data.' It offers no additional behavioral context such as the scope of deletion, irreversibility, or whether confirmation is required. Since annotations already disclose the destructive nature, the description adds little value.

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 brief but poorly structured. The phrase 'Delete series editor' is confusing and does not communicate the tool's purpose effectively. The warning is redundant with the annotation. While short, it does not provide clear, useful information in a well-structured way.

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 is a destructive bulk operation with a free-form body parameter and no parameter docs. The description fails to explain what the body should contain, what 'bulk delete series' entails, or what the output/return behavior is. Given the complexity and the presence of an output schema, the description is severely incomplete.

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 exposes a single 'body' object with no description and additionalProperties allowed (0% coverage). The description does not mention the parameter at all. There is no explanation of what should be placed in the body (e.g., series IDs or filters), leaving the agent unable to construct a valid request.

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 says 'Delete series editor' which is ambiguous and does not clearly state the tool's function as a bulk delete operation. It does not explicitly mention 'bulk' or 'series' as the target resource, and the word 'editor' is confusing. The warning 'this deletes data' is generic and doesn't clarify what data is affected.

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. It does not mention prerequisites, typical use cases, or exclusions. Given sibling tools like sonarr_delete_series (single delete) and sonarr_bulk_update_series, there is no differentiation or context about bulk deletion.

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