radarr_get_downloadclient_schema

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

Annotations already include readOnlyHint=true, and the description's 'Return' confirms a read operation. The description adds 'available fields/options,' which clarifies the response content but does not disclose additional behavioral details such as pagination, errors, or prerequisites. With annotations present, this modest extra context yields a score of 3.

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 single, efficient sentence that front-loads the action and resource. No wasted words or irrelevant details.

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?

The tool is very simple (no parameters, output schema provided), and the description fully captures its purpose. No additional context is necessary for an agent to select and invoke this 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 input schema has zero parameters, so there is nothing to document. The description adds no parameter information but is not required to; the baseline for zero-parameter tools is 4, and the description does not harm or miss anything.

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 uses a specific verb ('Return') and names the resource ('downloadclient schema'), clearly indicating this tool fetches the schema for download clients. It distinguishes itself from other schema tools like radarr_get_indexer_schema by naming 'downloadclient' explicitly.

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 this tool is used when you need the available fields/options for a download client, but it does not explicitly state when to use it versus alternatives like list_downloadclient or create_downloadclient. No exclusions or alternative tool references are provided, so usage guidance is only implied.

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