sonarr_update_config_downloadclient

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

Annotations already indicate readOnlyHint=false, so the 'WRITE' message adds little beyond what structured data provides. It does not disclose specific effects, reversibility, permissions, or other behavioral traits beyond a generic 'modifies your Sonarr instance'.

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 brief and front-loaded with the main action in the first sentence. The WRITE warning adds useful emphasis, though it is slightly redundant with annotations, so it is efficient but not minimal.

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 has an output schema so return values are presumably covered, but input semantics are under-specified. For an update operation with a free-form body, the description fails to explain required structure or suggest that the agent should first retrieve the existing config, making it incomplete for correct invocation.

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 description provides no explanation of the 'id' or 'body' parameters. The 'body' is an open object with additionalProperties, but an agent cannot know what fields are expected without further documentation.

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 the tool updates download client config, using a specific verb and resource. It distinguishes from sibling tools like sonarr_update_config_indexer, though it could be confused with sonarr_update_downloadclient, so it's not fully differentiated.

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?

No guidance on when to use this tool vs alternatives like sonarr_update_downloadclient or sonarr_update_config_host. The only hint is 'WRITE' which implies it is for modifications, but no explicit context or exclusions.

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