radarr_test_all_importlist

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

The description notes 'WRITE: this modifies your Radarr instance,' which is somewhat consistent with readOnlyHint=false, but it adds little beyond the annotation. It fails to explain what modifications occur, what 'force_test' means, or any side effects like triggering external notifications. The 'optionally force_test' phrase is mentioned without explanation, adding confusion rather than clarity.

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, but it is not effectively structured. The phrase 'Test testall' is an awkward, machine-generated fragment that sacrifices clarity for brevity. The WRITE warning is a useful separate sentence but the main description would benefit from rephrasing.

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?

Given that this is a simple no-parameter tool, a clear one-liner could suffice. However, the description fails to state the core purpose (testing all import lists) and offers no alternatives or context. The mention of force_test without schema support adds incompleteness, and the output schema is not sufficient to compensate for the unclear prose.

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 defines zero parameters, and the baseline should be 4. However, the description mentions 'optionally force_test', implying a parameter that does not exist in the schema. This is misleading and harms the agent's ability to understand the expected input. The description should not reference parameters that are not in the structured schema.

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 testall (optionally force_test)' which is confusing and does not clearly identify that the tool tests all import lists. The verb+resource is not explicit, and 'testall' is an odd term that doesn't make sense without prior knowledge. It also doesn't distinguish this from sibling tools like radarr_test_importlist which tests a single import list.

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 about when to use this tool versus alternatives such as radarr_test_importlist or radarr_test_all_indexer. There is no mention of whether this is for batch testing or when a user would need to test all import lists versus a specific one.

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