cleanuparr_update_download_cleaner_config

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

The description clearly says 'Replace', which implies the entire config is overwritten, adding behavioral context beyond the destructiveHint annotation. It also lists the specific fields affected, which helps the agent understand the scope of the mutation, though it stops short of detailing side effects or consequences of omitted fields.

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 no filler. It immediately states the action and the key parameters, earning its place without redundancy.

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?

Given the presence of an output schema and a a destructiveHint annotation, the description covers the essential purpose and key fields. It could be more complete by mentioning that this is a full configuration replacement or providing example values, but for a simple config update tool it is reasonably sufficient.

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 schema provides only a generic 'config' object with additionalProperties:true and no descriptions (0% coverage). The description compensates somewhat by listing the expected sub-fields, but it does not explain their types, formats, or defaults, so the semantic burden is only partially lifted.

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 'Replace' with a clear resource 'download cleaner config' and enumerates the fields involved (enabled, cronExpression, useAdvancedScheduling, ignoredDownloads). This distinguishes it from sibling tools like update_queue_cleaner_config and makes the purpose unmistakable.

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 explicit guidance is provided on when to use this tool versus alternatives such as get_download_cleaner_config or other update_*_config tools. The description gives no context about conditions, prerequisites, or exclusions, leaving the agent to infer usage from the name.

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