sonarr_delete_queue

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

The annotation already indicates destructiveHint=true, and the description merely restates this with 'DESTRUCTIVE: this deletes data.' It adds no context beyond the annotation, such as what exactly gets deleted, whether it affects the download client, or side effects of the boolean parameters.

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 two short sentences, front-loading the primary action and a clear destructive warning. While this is appropriately compact, the second sentence adds little beyond the annotation but still reinforces important safety information.

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?

With five parameters, a destructive operation, and no parameter descriptions, the description is insufficiently complete. It does not explain the significance of each flag, the scope of deletion, or the relationship to bulk operations, leaving significant gaps for an agent to correctly invoke the tool.

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 does not explain any of the five parameters (id, blocklist, change_category, skip_redownload, remove_from_client). The description only mentions 'queue items' without elaborating on how the parameters alter behavior, leaving the agent without necessary semantic information.

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') and the resource ('download client queue items'), which is specific enough to distinguish from many other tools. However, it does not distinguish itself from the sibling tool 'sonarr_bulk_delete_queue', which also deletes queue items, so it only partially differentiates.

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 like sonarr_bulk_delete_queue or sonarr_grab_queue_item. There is no mention of single-item vs bulk deletion or any context for choosing this tool over siblings.

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