lidarr_download_clients

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

With no annotations, the description carries the full transparency burden. It explicitly marks operations as WRITE or DESTRUCTIVE, including non-obvious behaviors like test operations modifying the instance. It does not disclose additional details like permissions or rate limits, but the safety profile is well covered.

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 efficiently structured: a one-sentence overview followed by a bullet-style list of operations with minimal but sufficient detail. Each line is concise and the layout makes scanning easy, with no redundant phrasing.

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 complexity of a dispatcher with 11 operations, the description covers all operations, their purposes, and safety flags. It does not explain return values or error cases, but the presence of an output schema reduces that need. Overall it provides enough context for an agent to use 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 coverage is 0%, so the description must compensate. It explains that 'arguments' is a dict matching each operation and gives hints like 'body carries ids' or 'body is a list of resources', but it does not specify exact fields for each operation. This is moderately helpful but leaves many parameter details unresolved.

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 clearly states it handles 'lidarr download clients operations' and enumerates all 11 specific operations with distinct verbs (list, get, create, update, delete, test, etc.). This distinguishes it from sibling tools that cover other Lidarr domains.

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 clear context that this tool is for download client management, and each sub-operation is described with its role. It does not explicitly mention when not to use it or point to alternatives, but the scope is unambiguous relative to siblings.

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