qbittorrent_torrents_remove_trackers

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

Annotations state readOnlyHint=false, indicating a mutating operation, and destructiveHint=false. The description adds the behavioral trait that it specifically removes trackers, which is beyond the annotations but does not disclose side effects, reversibility, or error behavior. It is adequate but minimal.

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 two short sentences, front-loaded with the primary action. It includes a necessary parameter detail (pipe delimiter) without verbose filler, though it could be slightly more structured by separating purpose from parameter explanation.

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?

This is a simple mutation tool with an output schema present. The description covers the essential input semantics (hash, pipe-separated URLs) and the operation's scope. Gaps like return format or error conditions are less critical given the simple nature and the presence of an output schema, so a high score is warranted.

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 provides no descriptions for the two parameters (0% coverage). The description compensates for one parameter ('urls') by explaining the pipe-separated format, but the 'hash' parameter is left unexplained. This partial coverage justifies a score slightly above baseline.

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 resource ('trackers from a torrent'), clearly distinguishing it from sibling tools like qbittorrent_torrents_add_trackers and qbittorrent_torrents_edit_tracker. It unambiguously states what the tool does.

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 does not explicitly state when to use this tool vs alternatives, but the purpose is clear enough that an agent can infer it is for removing trackers from a torrent. There is no exclusion or mention of alternatives, so it receives a middle score for implied usage.

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