qbittorrent_get_torrents

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

No annotations are provided, so the description carries the full behavioral burden. It usefully enumerates the returned fields, but says nothing about read-only safety, whether results are paginated or bounded, or authentication needs. That is a modest but real gap for a list endpoint.

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?

Two tight sentences with the primary capability front-loaded; nothing is wasted. The trailing parenthetical of state values is somewhat redundant against the schema's enum and slightly inaccurate, but the sentence still earns its place as a usage cue.

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?

With no output schema, the description correctly compensates by naming the returned fields, and all parameters are optional with full schema coverage. The main missing piece is read-only/pagination behavior, which nothing else supplies given the absence of annotations.

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 schema already documents all four parameters and the baseline is 3. The description only elaborates on the state filter, and its value list ('uploading, ... stalled') is inconsistent with the schema's enum ('seeding, stalled_uploading, stalled_downloading'), which adds ambiguity rather than value for tag, sort, and category.

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 ('List all torrents') plus the fields returned (status, progress, speed, seeds, peers). It is distinguishable from the singular qbittorrent_get_torrent_info sibling by the 'all torrents' framing, though it never names that sibling explicitly.

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 word 'Optionally filter by state' implies the tool works fully without arguments and that filtering is the main usage pattern, but there is no when-to-use versus when-to-prefer qbittorrent_get_torrent_info guidance or any prerequisites. Usage is implied rather than stated.

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