sonarr_delete_downloadclient

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

The description repeats the destructive hint already provided by annotations (destructiveHint=true, readOnlyHint=false) by stating 'DESTRUCTIVE: this deletes data.' It adds no new behavioral context such as specific data impacted, side effects, or required permissions. The description is consistent with annotations, so no contradiction.

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 with two sentences. The first sentence states the action clearly, but the second sentence ('DESTRUCTIVE: this deletes data.') is redundant given the annotations and the verb 'Delete'. Still, it is concise and front-loaded with the core purpose.

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?

Despite having an output schema, the description lacks important context: it does not clarify the 'id' parameter, does not differentiate from the bulk delete variant, and offers no warning about the scope of the deletion. This makes the tool under-specified for an agent that must decide correct usage.

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 schema has one required parameter 'id' (integer) with zero description coverage. The tool description does not explain what this id refers to, leaving the agent without guidance on how to determine the correct download client ID. This is critical for a destructive operation.

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 the action ('Delete') and resource ('download clients'), making the core purpose understandable. However, it does not distinguish from the sibling tool 'sonarr_delete_downloadclient_bulk', which also deletes download clients, leaving ambiguity about single vs. bulk deletion.

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?

There is no guidance on when to use this tool versus the bulk-delete sibling or other download client tools. No prerequisites, conditions, or alternative scenarios are mentioned. The only extra note is the destructive warning, which is not usage guidance.

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