radarr_get_downloadclient

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

The readOnlyHint annotation already indicates this is a safe read operation. The description consistently says 'Fetch' and adds no extra behavioral context (e.g., not-found behavior or response format), which is acceptable for a simple read tool but does not go beyond the annotation.

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, front-loaded sentence with zero wasted words. It states the action, resource, and scope immediately.

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?

For a simple one-parameter, read-only get-by-id tool, the description is complete. The output schema exists, so return values don't need explanation, and there are no nested objects or additional constraints requiring elaboration.

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 only says 'by id,' which maps to the schema's 'id' property but adds little beyond the obvious. However, since there is only a single integer parameter named 'id,' the description is adequate for a self-explanatory field.

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 ('Fetch') and resource ('downloadclient') with a clear scope ('single ... by id'). It distinguishes from list/get operations like radarr_list_downloadclient and radarr_get_downloadclient_schema by specifying exact retrieval of a single item by identifier.

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 when you need one specific download client by id, but it does not explicitly state when not to use it or mention alternatives. Sibling tools like radarr_list_downloadclient would be the obvious alternative for fetching all, but no such guidance is provided.

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