cleanuparr_get_queue_cleaner_config

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

The description is consistent with the readOnlyHint=true annotation and adds no contradictory information. It does not disclose any behavioral details beyond what the annotation already provides, but for a simple getter with an output schema, the annotation is sufficient. No extra context is added.

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 short sentence with no filler, and the verb 'Get' is front-loaded. It is appropriately concise for a simple parameterless getter, though it could have added a little more context about what the configuration contains.

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 that the tool has no parameters and an output schema is present, this minimal description is sufficient for an agent to select and invoke it correctly. The context becomes clear from the tool name and sibling list; no further details are needed for successful 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?

The input schema has zero parameters, so schema coverage is 100% and there is nothing for the description to add. The baseline for zero parameters is 4. The description correctly avoids inventing parameter details.

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 the specific verb 'Get' and explicitly names the resource 'queue cleaner configuration', which clearly distinguishes this tool from sibling config getters like get_download_cleaner_config and get_dead_torrent_config. It unambiguously states the tool's function.

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 implies usage via the verb 'Get' – use when you need the queue cleaner configuration. However, it provides no explicit guidance about when not to use it or alternatives, such as mentioning the corresponding update_queue_cleaner_config. This is adequate but not explicit.

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