cleanuparr_update_queue_cleaner_config

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

The annotation already declares destructiveHint: true, and the description's use of 'Replace' reinforces the destructive, overwriting nature of the operation. However, it does not disclose additional behavioral details like whether unspecified fields are reset, whether a restart is required, or any side effects. The bar is lowered by annotations, so this is acceptable but not rich.

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 two sentences with no filler. It front-loads the action ('Replace queue cleaner config') and immediately enumerates the config fields, making it efficient and easily scannable.

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?

Despite having only one parameter, the description compensates for the schema's lack of detail by listing the config fields. An output schema exists, so return values don't need explanation. The tool's behavior is a simple replacement, and the description covers the essential information, though it omits details about optionality or defaults.

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?

With schema description coverage at 0% and only a generic 'config' object with additionalProperties: true, the description adds crucial meaning by listing the expected DTO fields: enabled, cronExpression, useAdvancedScheduling, failedImport, downloadingMetadataMaxStrikes, processNoContentId, and ignoredDownloads. This helps the agent know what keys to include, though it does not explain each field's type or purpose.

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' and specifies the resource 'queue cleaner config', making its function unambiguous. It clearly distinguishes from the read tool 'cleanuparr_get_queue_cleaner_config' and other config-update tools by naming the exact target.

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 does not provide explicit guidance on when to use this tool versus alternatives, such as when to update vs. get the config. Usage is implied by the tool name and purpose, but no exclusions or alternative recommendations are given.

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