sonarr_delete_indexer_bulk

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

The description adds a 'DESTRUCTIVE' warning, but this merely restates the destructiveHint annotation. It does not disclose what specific data is deleted (e.g., indexer definitions), whether the operation is reversible, or any additional context like permissions or rate limits.

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 verb, but the second sentence ('DESTRUCTIVE: this deletes data.') is redundant with the destructiveHint annotation and does not earn its place. Overall it's concise but not optimally structured.

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 under-specified: it doesn't explain the body parameter, what 'bulk' entails, or provide usage context. Even though annotations and an output schema exist, the tool is a destructive operation with an opaque open object parameter, requiring more detail to be safely and correctly invoked.

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 input schema has one 'body' object parameter with no description and 0% schema coverage. The tool description does not explain what the body should contain (e.g., an array of indexer IDs), leaving the agent completely without guidance for constructing 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 clearly states the operation ('Delete') and the resource ('indexer bulk'), and the name includes 'bulk' distinguishing it from sonarr_delete_indexer. However, the phrasing 'Delete indexer bulk' is awkward and doesn't explicitly say 'delete multiple indexers', so it's clear but not flawless.

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 like sonarr_delete_indexer or other bulk-delete tools. It doesn't mention prerequisites, the required body structure, or any exclusion criteria.

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