qbittorrent_torrents_list

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

The annotation already declares readOnlyHint=true, and the description aligns by describing a read-only listing operation. It adds behavioral nuance by explaining that empty category/tag values mean 'without category/tag', which is beyond the schema. It doesn't describe return format, but output schema covers that.

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 dense sentence with all key information present and no filler. It front-loads the purpose and then lists parameters in a logical order. It could benefit from bullet formatting but is appropriately concise.

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 the presence of a read-only annotation and an output schema, the description covers the essential usage aspects: filter options, category/tag semantics, sorting, reversal, paging, and hash selection. No critical gaps were identified for this list operation.

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 0%, so the description carries the full burden. It explains every parameter: filter values, category/tag semantics, sorting by response fields, reverse order, limit/offset paging, and hash selection. This adds substantial meaning beyond the bare 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?

The description opens with a specific verb ('List') and resource ('torrents'), and immediately clarifies it supports filters. This clearly distinguishes it from sibling tools as the primary listing 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?

The description explains the filtering, sorting, and paging capabilities, giving clear context for when to call this tool. However, it does not explicitly mention alternatives or exclusions relative to sibling tools like qbittorrent_torrent_properties or qbittorrent_sync_maindata, so it relies on implied usage.

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