sonarr_delete_queue_item

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

With no annotations, the description must disclose behavior. It covers the dry-run mode, batch deletion by download_id, and side effects like client deletion and blocklisting. It lacks mention of error handling but is otherwise thorough.

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 five sentences long, each serving a clear purpose: purpose, parameter exclusivity, batch behavior, additional options, and dry-run feature. No wasted 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's complexity (5 parameters, destructive action) and the presence of an output schema, the description covers all necessary behavioral and usage aspects. It is complete for agent decision-making.

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%, yet the description explains all five parameters: queue_id/download_id exclusivity, confirm for dry-run, remove_from_client and blocklist booleans. It adds meaning beyond the schema, such as the constraint and the effect of each parameter.

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 'Remove item(s) from the Sonarr download queue' with a specific verb and resource. While it doesn't explicitly distinguish from sibling 'radarr_delete_queue_item', the tool name prefix 'sonarr_' inherently differentiates it.

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 explicit guidance: 'Provide EXACTLY ONE of: queue_id or download_id' and explains the dry-run preview via 'confirm', the effects of 'remove_from_client' and 'blocklist'. It tells exactly when to use each parameter and the consequences.

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