radarr_test_indexer

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

The description explicitly states 'WRITE: this modifies your Radarr instance,' which is a valuable side-effect warning beyond the annotations' readOnlyHint=false. It also discloses that it returns validation results. However, it does not elaborate on what exactly is modified or what side effects occur.

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 concise with three short phrases, and the write warning is front-loaded after the initial action. However, the phrase 'Test test' is a clarity problem that makes the conciseness less effective than it could be.

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 an output schema and an arbitrary 'body' object, the description omits essential context: what resource is being tested, how the indexer is identified in the body, and how this relates to radarr_test_all_indexer. The agent is left without enough information to invoke the tool correctly.

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 0% description coverage, and the description only names 'force_test' without explaining what it does. The 'body' parameter, which likely carries the indexer identifier, is completely ignored. The description adds no meaningful semantic value over the 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 test (optionally force_test)' but fails to identify the resource (indexer) being tested. 'Test test' is a confusing placeholder that neither restates the tool name clearly nor conveys the action. It mentions 'Returns validation results' but does not distinguish this from siblings like radarr_test_all_indexer.

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 or how it differs from alternatives such as radarr_test_all_indexer or radarr_test_downloadclient. There is no mention of prerequisites, typical use cases, or exclusionary scenarios.

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