remove_queue_items

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the important default side effect that the download is also removed from the download client, and explains the blocklist and skip_redownload options. However, it omits the change_category behavior and does not explicitly warn about 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?

The description is two sentences with no filler, leads with the primary action, and packs the key behavioral defaults into compact, useful phrasing. Every sentence earns its place.

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?

For a five-parameter tool with a fully described schema, the description covers the most important behavioral consequences. The main gaps are that change_category is not mentioned and there is no statement about what the tool returns, which would be helpful since no output schema exists.

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?

Schema description coverage is 100%, and the schema already provides meaningful descriptions for all five parameters. The description adds context around defaults and consequences, but it does not significantly extend the parameter-level meaning beyond what the schema already contains.

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 uses a specific verb ('Remove'), a clear resource ('items from the queue'), and indicates it can handle one or more items. It is immediately distinguishable from queue-management siblings like grab_queue_items and from movie deletion tools.

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 implies this is the tool for removing queue items, but it does not explicitly state when to use it versus alternatives, nor does it mention when not to use it. There is no comparison to related tools such as remove_blocklist_items or delete_movies.

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