qbittorrent_rss_remove_rule

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

Annotations already indicate destructiveHint=true, so the destructive nature is known. The description adds no extra behavioral context beyond what annotations provide, such as irreversibility or effects on active downloads, but it is consistent with the annotations.

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?

One short sentence that is front-loaded and free of unnecessary words. It efficiently conveys the core action without repetition or filler.

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 tool is simple and the description plus annotations cover the basic action, but it lacks details about failure behavior, whether deletion is permanent, and guidance on alternatives. These gaps, though not critical for such a straightforward operation, prevent a higher completeness score.

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's single parameter, rule_name, has no description coverage, and the tool description does not elaborate on it. While the name and tool purpose make it inferable that rule_name identifies the rule, no explicit format or identifier semantics (name vs ID) are given.

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 'Remove' and identifies the resource as 'auto-downloading rule', clearly distinguishing it from related RSS tools like qbittorrent_rss_set_rule or qbittorrent_rss_rename_rule. It unambiguously states the operation.

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. It does not mention that rules are created or modified via qbittorrent_rss_set_rule, nor does it explain any prerequisites like the rule existing before removal.

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