cleanuparr_delete_queue_rule

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

The destructiveHint annotation already signals destructiveness, and the description confirms it by saying 'Delete'. It adds the resource scope ('stall or slow queue rule') and that the identifier is a GUID, but does not disclose permanence, effects on related data, or any other behavioral traits beyond what annotations provide.

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, efficiently worded sentence with the verb front-loaded. Every word contributes value, and there is no repetition or unnecessary detail.

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 there is an output schema, return values are covered, but the description is incomplete regarding the 'kind' parameter, which is required and unexplained. It also does not mention where to find the GUID (e.g., via list_queue_rules). For a simple tool with two required parameters, this leaves notable 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?

The schema description coverage is 0%, and the description only partially adds meaning. It clarifies that rule_id is a GUID, but the required 'kind' parameter is completely unexplained. The description does not compensate for the lack of schema descriptions, leaving a significant ambiguity about what values 'kind' accepts.

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 identifies the verb (Delete) and the specific resource (stall or slow queue rule), and specifies the identifier (GUID). This distinguishes it from other delete tools targeting different resources like seeding rules or download clients.

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 by stating what the tool does, but provides no explicit guidance on when to use it versus alternatives, no preconditions, and no hint to first list rules to obtain the GUID. It relies on the tool name and obviousness of the delete operation.

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