radarr_delete_queue_item

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

Describes the behavioral traits: it removes items from queue, can delete from client (remove_from_client), and can blocklist the release. Annotations are absent, so description carries burden; it adequately discloses side effects, though could mention irreversibility.

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?

Concise and well-structured: front-loaded purpose, then brief parameter groups. Every sentence provides value without redundancy. Efficiently uses bullet points for clarity.

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?

Complete coverage for a deletion tool with 5 parameters and mutual exclusivity. Explains when to use each identifier, the dry-run vs actual deletion, and the effect of boolean flags. Output schema exists but is not needed.

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?

With 0% schema coverage, description explains all five parameters: queue_id, download_id, remove_from_client, blocklist, confirm. It clarifies mutual exclusivity and dry-run behavior, adding meaning beyond bare schema.

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?

Description clearly states that the tool removes item(s) from Radarr download queue, specifically targeting stuck/failed downloads. It uses the verb 'remove' and resource 'queue item', distinguishing it from sibling tools like radarr_delete_movie.

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?

Explicitly provides when to use each parameter: queue_id for single item, download_id for all items sharing that downloadId. Also explains the dry-run behavior using confirm flag and the effect of remove_from_client and blocklist, offering clear guidance on usage.

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