sonarr_delete_downloadclient_bulk

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

The description explicitly says 'DESTRUCTIVE: this deletes data,' which replicates the annotation's destructiveHint=true without adding additional context. It doesn't disclose specifics such as what is permanently removed, whether confirmation is needed, or side effects beyond the general destructive hint.

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 short and front-loaded with the action, but the second sentence repeats the annotation's destructive hint, which slightly reduces its value. Still, it is well-structured and avoids unnecessary 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?

For a bulk deletion tool with a mutable operation and a free-form body parameter, the description is inadequate. It doesn't specify parameter format, selection criteria, or behavior beyond the general destructive warning. An output schema exists, but the input side is critically undocumented.

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?

The input schema has a single 'body' object with no property descriptions and 0% schema coverage. The description does not explain what the body should contain (e.g., IDs of download clients to delete), leaving the agent with no guidance for constructing the request.

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 a clear action ('Delete') and resource ('downloadclient bulk') with a specific scope. It is distinguishable from sibling tools like the singular sonarr_delete_downloadclient by the 'bulk' qualifier. The destructive warning adds clarity.

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 a bulk operation through the name and 'bulk' in the description, but doesn't explicitly state when to use this tool versus alternatives like sonarr_delete_downloadclient for single deletions. No explicit context or exclusions are provided.

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