cleanuparr_update_unlinked_config

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

The annotation destructiveHint=true already signals mutation. The description adds that only the listed settings are replaced, giving some scope. However, it does not explain whether this is a full replacement of the config object or just those fields, nor does it mention side effects or permission requirements.

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 sentence that conveys the essential information in a compact form. No filler or redundant phrasing, and the list of settings is directly useful.

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 description provides the core settings for the unlinked config, and an output schema exists, reducing the need to explain return values. However, the description lacks detail about how the config object is structured, whether 'replace' means the entire config is overwritten, and how download_client_id is used. It is adequate but leaves gaps.

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%, so the description must compensate. It lists the key fields inside the config object, which helps understand that parameter. However, it does not describe download_client_id, nor does it define the meaning or format of each listed field. The config object is open-ended (additionalProperties true), so the list is informative but incomplete.

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 action 'Replace unlinked settings' and enumerates the specific fields affected (enabled, targetCategory, useTag, ignoredRootDirs, categories). This distinguishes it from sibling tools that update other config types, such as update_queue_cleaner_config or update_dead_torrent_config.

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 is provided on when to use this tool versus alternatives, when not to use it, or any prerequisites such as needing to fetch the current config first. The description implies a straightforward update but lacks explicit usage context.

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