prowlarr_download_clients

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

With no annotations, the description carries the full burden. It discloses each operation's action (delete, create, list, test) and adds behavioral details such as 'force_save bypasses validation' and 'Read this before creating or updating a download client'. It stops short of covering permissions, error handling, or reversibility, but the per-operation behavior is well conveyed.

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 uses a scannable list format with each operation on its own line, providing the signature and a one-line effect. Every entry adds value, and the opening lines establish the overall usage pattern without redundancy.

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?

All 11 operations are documented with their parameters and prerequisites, and an output schema exists to cover return formats. The description does not delve into argument object internals, but the references to DownloadClientResource and schemas cover the essentials, making it sufficiently complete for a dispatcher tool.

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 coverage is 0% and the input schema only has generic operation/arguments fields. The description compensates by listing each operation's signature with parameter names and types (body, id, force_save), and refers to prowlarr_list_download_client_schemas for body structure. This gives the agent meaningful guidance beyond 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 explicitly states this tool handles 'download clients operations on Prowlarr' and then lists every operation with a specific verb and resource (e.g., 'Bulk-delete download clients', 'Create a download client'). This fully differentiates it from sibling tools focused on indexers, applications, system, etc.

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 opening line explains how to invoke the tool (pass an operation and arguments dict), and there are helpful hints like reading schemas before creating/updating and force_save bypassing validation. However, it does not explicitly state when to prefer this tool over alternatives or when not to use it, so the guidance is implied rather than explicit.

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