autobrr_download_clients

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

Without annotations, the description takes on the burden of disclosing side effects. It explicitly marks create, test, and update as WRITE operations and delete as DESTRUCTIVE, which is valuable. It also adds contextual detail like the *arr-specific tags operation.

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 a concise bullet list with each operation's signature and a short description, front-loaded with usage instructions. Every line provides necessary information for selecting an operation.

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 dispatcher pattern with seven sub-operations, the description covers all operations and flags dangerous ones, but it lacks a concrete usage example and detail on how arguments map to each operation. The presence of an output schema reduces the need to explain return values.

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 only offers generic `operation` and `arguments` fields, with 0% coverage. The description compensates by listing each operation's signature (e.g., client_id, body={}), giving agents a template for constructing the arguments dict. However, it does not explain the structure or required fields of the body dict itself.

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 identifies the tool as handling download client operations for autobrr, listing all seven sub-operations with one-line summaries. This distinguishes it from sibling tools that handle other autobrr resources.

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 implies usage by naming each operation and its parameters, but it does not explicitly state when to prefer this tool over alternatives or when not to use it. No exclusions or alternative tool references are provided.

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