qbittorrent_rss_refresh_item

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

Annotations already indicate the operation is not read-only (readOnlyHint=false) and not destructive (destructiveHint=false). The description adds the 'force' aspect, which implies bypassing normal refresh conditions, providing a bit of behavioral context. However, side effects, permissions, or rate limits are not disclosed, so credit is limited.

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, tightly written sentence ('Force-refresh an RSS folder or feed.') that is front-loaded with the action verb and resource. It contains no filler or redundant information, making it highly efficient.

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?

For a simple tool with an output schema, the description sufficiently captures the essential purpose. It may not cover edge cases like error conditions or exact path format, but the provided annotations and output schema fill in some gaps. Overall, the description is adequate for selecting and invoking the tool correctly.

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 has one required parameter 'item_path' with no description (0% coverage). The description compensates by indicating that item_path identifies a folder or feed, giving semantic meaning to the parameter. While it doesn't detail formats or examples, it directly maps the parameter to the tool's domain.

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 states the action ('Force-refresh') and the resource ('an RSS folder or feed'). This distinguishes it from sibling tools like qbittorrent_rss_remove_item, qbittorrent_rss_move_item, and qbittorrent_rss_mark_as_read, which have different verbs and purposes.

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 the tool is used to refresh RSS folders or feeds but does not explicitly mention when to use it versus alternatives, nor does it provide exclusions or prerequisites. The clear purpose gives context, but alternatives are not addressed.

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