manage_stalled_downloads

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

With no annotations, the description carries the behavioral disclosure burden; it does indicate the tool changes download state (isolate, pause, blocklist) rather than being read-only. However, it omits the destructive PURGE_STALLED side effect and the re-search flag, and gives no indication of reversibility or permissions; the schema's action descriptions partially compensate.

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?

A single front-loaded sentence names the resource, the defect condition, and the possible actions with no filler. Every phrase earns its place.

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 two-parameter tool with a rich schema, the definition is mostly adequate, but there is no output schema and no annotation-level safety information. The description does not specify what AUDIT returns in practice or the full effects of PURGE_STALLED beyond the schema, so an agent has to rely on enum descriptions for side effects.

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?

Schema description coverage is 100%, so the baseline is 3; the action enum and minSpeedKbps descriptions are already explicit. The description adds only the 'below threshold' concept, which loosely maps to minSpeedKbps but adds no syntax or format detail beyond the schema.

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?

States a specific verb and resource: scans qBittorrent download queues and targets stalled items below a speed threshold. It is clear about the domain and intent, though it does not explicitly distinguish itself from siblings and its 'pause or blocklist' wording does not fully match the AUDIT/PURGE_STALLED action enum.

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 qBittorrent queue context and below-threshold condition imply when to use it, but there is no explicit when-to-use or when-not-to-use guidance, nor any named alternative. An agent must infer that this is for stalled-download management rather than being told.

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