radarr_bulk_delete_indexer

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

The annotation destructiveHint=true already declares the destructive nature, and the description merely repeats it with 'DESTRUCTIVE: this deletes data.' No additional context is provided, such as irreversibility, affected resources, or authorization needs.

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 exceptionally concise, using a single sentence and a short warning. It is front-loaded and contains no filler, earning full marks for brevity.

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?

Despite having an output schema, the description lacks critical usage details: it does not explain how the bulk delete request should be structured, what response to expect, or any edge cases. The input schema is vague, and the description does not compensate for this incompleteness.

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 has a single 'body' object parameter with no description and additionalProperties true. The description does not explain what should be placed in 'body' (e.g., list of indexer IDs), leaving the parameter entirely undefined.

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 states 'Bulk delete indexers' with a clear verb and resource, and the 'DESTRUCTIVE' warning reinforces the tool's purpose. It distinguishes from single-delete tools like radarr_delete_indexer by specifying 'bulk'.

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?

No guidance is provided on when to use this tool versus alternatives such as radarr_delete_indexer or radarr_bulk_update_indexer. There is no mention of prerequisites, id formats, or how to select multiple indexers, leaving the agent to infer usage.

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