radarr_delete_queue

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

Annotations already mark destructiveHint=true and readOnlyHint=false. The description adds a human-readable warning 'DESTRUCTIVE: this deletes data,' which reinforces the safety profile but does not disclose additional behavior such as the effect of remove_from_client or other parameters. Since annotations cover the core destructive nature, this is adequate but not enhanced.

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 extremely concise with a single clear sentence and a separate warning. It is well-structured and front-loaded, but its brevity comes at the cost of omitting essential usage details. Still, as a structure, it earns points for clarity and not wasting words.

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 has 5 parameters, a destructive nature, and exists alongside a bulk-delete sibling, the description is incomplete. It does not explain the effect of parameters like blocklist or remove_from_client, nor does it differentiate from radarr_bulk_delete_queue. An output schema exists but the description fails to provide necessary operational context beyond the basic action.

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 0% and the description provides no explanation of any of the 5 parameters (id, blocklist, change_category, skip_redownload, remove_from_client). The description must compensate for the low coverage but does not mention any parameter semantics, leaving the agent to guess meanings.

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 ('Delete download client queue items') with a specific verb and resource. It distinguishes itself from sibling tools like radarr_bulk_delete_queue by implying singular deletion and from radarr_grab_queue_item which is a different action. The destructive warning also reinforces the tool's intent.

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. It does not mention radarr_bulk_delete_queue for batch deletion or explain conditions for single-item deletion. The description lacks any contextual or exclusionary guidance, 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.