radarr_bulk_delete_queue

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

The description's 'DESTRUCTIVE: this deletes data' merely restates the destructiveHint annotation without adding new behavioral context. It does not disclose specifics like irreversibility, impact on download client, or any rate limits or authentication requirements. Since annotations already cover destructive behavior, the description adds minimal transparency 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 exceptionally concise at two short sentences, front-loaded with the core action. However, the second sentence is redundant with the annotations, and the under-specification means it sacrifices essential detail 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?

Given the tool's complexity (5 params, a free-form body object) and destructive nature, the description is insufficiently complete. It lacks any mention of parameter semantics, the output schema, or behavioral caveats, leaving the agent with critical gaps in understanding.

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 5 parameters with 0% description coverage, and the description provides no explanation of any parameter. Users are left without guidance on what 'body', 'blocklist', 'change_category', 'skip_redownload', or 'remove_from_client' do, making the tool significantly harder to use correctly.

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 action ('Bulk delete') and the resource ('download client queue items'), making the tool's purpose immediately obvious. It also distinguishes it from sibling tools like radarr_delete_queue (singular) and radarr_grab_queue_bulk, which serve different actions.

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 explicit guidance on when to use this tool versus alternatives, such as radarr_delete_queue for single deletions or other bulk delete tools. While the 'DESTRUCTIVE' warning implies caution, it does not articulate scenarios for use or prerequisites.

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