radarr_test_downloadclient

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

Annotations indicate readOnlyHint:false and destructiveHint:false; the description explicitly warns 'WRITE: this modifies your Radarr instance', adding a useful behavioral caution beyond the annotations. It also notes returns validation results, which clarifies outcome. No contradiction with annotations.

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 short and front-loaded, but the opening 'Test test' is awkward and arguably wastes the first sentence. It contains three useful segments (test action, force_test option, WRITE warning) but could be more structured.

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 tool with a free-form body and nested objects, the description lacks essential details about the request body format, how to specify which download client is being tested, and what 'validation results' contain. The WRITE warning helps but does not compensate for missing operational details.

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?

Input schema has 0% description coverage. The description only mentions `force_test` as optional, giving minimal semantic context for that parameter. The `body` object parameter (additionalProperties:true) is entirely unexplained, so most parameters lack meaning.

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 says 'Test test (optionally force_test)' which is vague and nearly tautological with the tool name. It does not explicitly state it tests a download client, nor does it distinguish from sibling `radarr_test_all_downloadclient`. The addition 'Returns validation results' provides some clarity, but overall purpose is poorly conveyed.

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 vs alternatives like `radarr_test_all_downloadclient` or `radarr_create_downloadclient`. The description simply states the action without context, prerequisites, or exclusions.

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