sonarr_create_downloadclient_test

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

The description says 'WRITE: this modifies your Sonarr instance.' but this simply repeats the annotation readOnlyHint=false. It adds no additional behavioral context beyond the annotation—no mention of what exactly is modified, side effects, or prerequisites. With annotations present, the description should add value like specifics about the test operation, but it does not.

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 only two sentences, but the second sentence is redundant with the annotation and does not earn its place. The first sentence is a tautological restatement. This is under-specification rather than effective conciseness.

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 the tool's complexity (body object, boolean flag) and the lack of any parameter or usage guidance, the description is grossly incomplete. The output schema exists but the description does not explain what the tool returns or what the test does, leaving the agent without enough information to invoke it 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?

Schema description coverage is 0%, so the description must compensate. It does not mention 'body' or 'force_test' at all. The agent has no idea what to put in the body object or what force_test controls. This is a complete lack of parameter guidance.

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 'Create downloadclient test' is essentially a tautology of the tool name 'sonarr_create_downloadclient_test', replacing underscores with spaces. It does not explain what a 'downloadclient test' is or what the test does. It distinguishes nothing from siblings like 'sonarr_create_downloadclient_testall'.

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?

The description provides absolutely no guidance on when to use this tool versus alternatives. It does not mention that this tests a single download client configuration, nor does it contrast with 'testall' or other test tools. There is no usage context or exclusions.

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