sonarr_remove_from_queue

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

No annotations are provided, so the description must disclose behavioral traits independently. It mentions the blocklist option's purpose (prevent re-grabbing) but omits significant behaviors such as the default removal from the download client (removeFromClient=true) and any consequences for the item in Sonarr. This leaves the agent without a full picture of side effects.

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 a single, well-structured sentence that immediately conveys the tool's purpose and key optional behavior. It avoids redundancy and unnecessary words, making it highly concise and front-loaded.

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 mutation tool with no annotations and no output schema, the description is incomplete. It does not explain operational behavior such as whether removal from the download client is intended (despite the schema default), how the queue item is affected, or when to prefer this tool over alternatives. The schema covers parameters but not the tool's broader context.

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 coverage is 100% for all three parameters, with detailed descriptions in the input schema. The description adds little beyond the schema, only restating the blocklist parameter's purpose without elaborating on ids or removeFromClient. This meets the baseline but does not exceed it.

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 specifies the action (remove) and the resource (Sonarr download queue), and distinguishes it from related tools such as sonarr_get_queue and sonarr_delete_from_blocklist. The phrase 'one or more items' also clarifies scope.

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 usage for removing items from the download queue, but it does not explicitly state when to use this tool versus alternatives like sonarr_get_queue or sonarr_delete_from_blocklist. There are no exclusions or conditional guidance, making the usage implied rather than explicit.

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