radarr_test_all_metadata

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

The description explicitly warns 'WRITE: this modifies your Radarr instance,' which is valuable beyond the annotations (readOnlyHint=false already indicates mutation). It also mentions return type ('validation results'). This adds meaningful context without contradicting 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 short and to the point, but the phrasing 'Test testall' is awkward and could be clearer. It is acceptable in length but lacks structural clarity.

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?

The tool is simple (no params, no output schema), but the description remains opaque: it does not clarify what 'testall' means or when to use it versus singular test_metadata. It provides a write warning but misses the core purpose explanation.

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 zero parameters, but the description mentions 'optionally force_test' without it appearing in the schema. This is misleading and creates ambiguity about whether the tool accepts any parameters. Since there are no parameters, a baseline of 4 would normally apply, but the contradiction with the schema reduces the score.

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 the action ('Test testall') but 'testall' is jargon from the API endpoint and not self-explanatory. Adding 'Returns validation results' clarifies the outcome, but it does not clearly state what is being tested (e.g., all metadata providers). It is not a full tautology, but it is vague.

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 provided on when to use this tool versus the similarly named radarr_test_metadata or other metadata-related tools. There is no mention of prerequisites, context, or alternatives.

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