prowlarr_bulk_delete_indexers

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

The destructiveHint annotation already signals destructive behavior, and the description simply echoes 'Bulk-delete' without adding specifics like permanence, irreversibility, or partial-failure semantics. No additional behavioral context is provided beyond what the annotation already states.

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?

Two short sentences, directly front-loaded with the tool's purpose and the key parameter detail. Every word earns its place; there is no fluff or repetition.

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 gives the core operation and identifies the body's expected type, but leaves out the exact structure of IndexerBulkResource (e.g., whether ids is an array, any optional fields). Given that an output schema exists and destructiveHint is annotated, it's minimally viable but could be more explicit about the body's format and any behavioral consequences.

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 only says 'body' is an object with no property descriptions, but the description adds that it should be an IndexerBulkResource with an ids property. This provides essential structural guidance that the schema lacks, though it doesn't fully specify the format of ids or other possible fields.

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 a specific action (bulk-delete) on a specific resource (indexers), distinguishing it from single delete and bulk update siblings. The phrase 'Bulk-delete indexers' is a specific verb+resource combination that leaves no ambiguity.

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 does not explicitly state when to use this tool vs alternatives like prowlarr_delete_indexer for single deletions or prowlarr_bulk_update_indexers for bulk updates. The 'bulk' prefix implies multiple indexers, but there is no guidance on scenarios, prerequisites, or when to choose this over other tools.

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