radarr_bulk_delete_downloadclient

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

The description's 'DESTRUCTIVE' warning merely echoes the destructiveHint=true annotation, adding no new information such as what data is deleted, irreversibility, or side effects. Since annotations already cover the destructive nature, the description provides no additional behavioral transparency.

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 highly concise, using two short sentences with no redundancies. While the destructive warning repeats the annotation, it is purposeful for emphasis. No wasted words, but it could have included more critical information without becoming verbose.

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 destructive bulk delete tool, the description lacks essential context about what payload is expected (e.g., list of IDs) and the consequences. The schema provides no guidance, and there is no explanation of return values or validation, making it only partially complete.

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 says nothing about the 'body' parameter. The schema only shows an open-ended object with additionalProperties, leaving the agent without any hint about required fields (e.g., IDs) or the request structure.

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 states the action clearly: 'Bulk delete downloadclient' with a specific verb and resource. It implies bulk vs. individual deletion, distinguishing it from siblings like radarr_delete_downloadclient, though it does not explicitly mention alternatives.

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 vs. alternatives (e.g., individual delete, bulk update). The destructive warning is a caution, not a usage guideline, and there are no prerequisites or contexts described.

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