radarr_update_config_importlist

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

Annotations already indicate readOnlyHint=false, and the description adds 'WRITE: this modifies your Radarr instance,' which reinforces that it is a mutation. However, it does not disclose what fields get updated, whether changes are reversible, or any permissions needed. This adds minimal value beyond the annotations.

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 extremely concise, with every word earning its place. The 'WRITE' label is front-loaded, but the body is under-specified, which is not a matter of conciseness but of completeness.

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?

With two parameters, one of which is a free-form body, and zero schema descriptions, the description fails to provide essential context for using the tool correctly. It does not mention the required id, what the body should contain, or any return value expectations, leaving the agent without enough information to invoke it properly.

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 provides no explanation of the 'id' or 'body' parameters. For a nested body object with additionalProperties true, this is completely inadequate.

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 states 'Update import lists' which is a clear verb and resource, but it does not specify that this is the config import list, making it ambiguous with the sibling tool radarr_update_importlist. It offers no differentiation from the many other import list tools.

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?

There is no guidance on when to use this tool versus alternatives. It does not mention that this targets config import list settings or exclude other update tools.

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