radarr_delete_downloadclient

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

The annotation destructiveHint=true already informs the agent that this operation is destructive. The description's 'DESTRUCTIVE: this deletes data' merely restates this annotation without adding new behavioral context such as irreversibility, impact on related settings, or confirmation requirements. No additional safety or side-effect information is provided.

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 extremely concise and front-loaded, with the core action stated in the first three words. However, the second sentence 'DESTRUCTIVE: this deletes data' is redundant with the destructiveHint annotation, so it does not earn its place. Still, overall it is appropriately brief for a simple delete operation.

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 simple delete tool, the description lacks essential context: no explanation of the 'id' parameter, no usage guidance, and no behavioral details beyond the annotation. The presence of an output schema does not compensate for missing parameter semantics and usage context. The tool is not complete enough for an agent to confidently invoke it.

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 defines a single required parameter 'id' as an integer, but the description provides no explanation of what this ID represents or how to obtain it. With 0% schema description coverage, the description completely fails to compensate, leaving the parameter semantics fully opaque.

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 downloadclient' clearly states the verb (delete) and resource (downloadclient), matching the tool name exactly. It distinguishes this from sibling tools like radarr_list_downloadclient, radarr_create_downloadclient, and radarr_update_downloadclient by specifying the delete action.

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 alternatives. It does not mention radarr_get_downloadclient for retrieving the ID, radarr_bulk_delete_downloadclient for bulk operations, or any prerequisites. The description only states the action without contextual usage advice.

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