sonarr_bulk_delete_queue

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

The description repeats the destructive warning already captured by the destructiveHint annotation, adding no new behavioral context. It does not explain what happens to downloaded files, how the 'remove_from_client' or other parameters affect the operation, or whether confirmation is required.

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 very concise at two short sentences, front-loading the primary purpose. However, the second sentence is redundant given the annotations, though it does not detract from the overall compact structure.

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—five parameters including a nested object, plus an output schema—the minimal description is insufficient for correct invocation. It lacks critical details about input structure and behavioral nuances, making it inadequate for an autonomous agent.

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?

With 0% schema description coverage, the description provides no explanations for the five input parameters. The agent gets no clue about what the 'body' object should contain or the meaning of the boolean flags, failing to compensate for the schema gaps.

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 'Delete queue bulk' clearly indicates a bulk delete operation on the queue, distinguishing it from the singular sonarr_delete_queue and the blocklist bulk delete. The verb and resource are explicit, though the wording is slightly awkward and does not explicitly mention 'items'.

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 given on when to use this tool versus alternatives like sonarr_delete_queue for individual deletions. There is no mention of use cases, prerequisites, or workflow context, leaving the agent without directional information.

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