radarr_create_downloadclient

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

The 'WRITE: this modifies your Radarr instance' warning adds little beyond the existing annotation readOnlyHint=false, which already signals a write operation. No additional behavioral traits such as dependencies, validation, or side effects are disclosed.

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 brief and front-loaded with the action ('Create downloadclient'). The additional warning sentence is short, though somewhat redundant with the annotations, but it does not add unnecessary verbosity.

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 creating a download client typically requires a structured body parameter, the description is incomplete. It fails to mention the need to obtain or construct the body schema, leaving the agent without enough context to invoke the tool correctly despite an output schema existing.

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%, and the description does not compensate for the generic 'body' object or 'force_save' boolean. The description provides no insight into what fields the body should contain or when force_save should be used.

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 explicitly states 'Create downloadclient' with a specific verb and resource, clearly distinguishing this from the many list/update/delete/test download client siblings. It lacks a bit of detail about what a downloadclient is, but the core purpose is unambiguous.

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 alternatives, or that one should consult radarr_get_downloadclient_schema first to build a valid body. The description only restates the action without any contextual usage instructions.

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