qbittorrent_torrents_set_force_start

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

Annotations indicate the operation is non-read-only and non-destructive. The description adds that it toggles a force-start state, but it does not clarify the boolean mapping (true vs false) or potential side effects like overriding the paused state. This is minimal but does not contradict annotations.

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 concise sentence, front-loaded with the action, and includes the key hash format scope ('pipe-separated or all'). No unnecessary words or repetition.

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?

The tool is a simple setter, but the description lacks an explanation of the force-start concept and how it differs from normal resume. It also omits the value-to-action mapping. With an output schema present, return details are not needed, but the gaps in parameter and behavioral clarity reduce completeness.

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 must explain parameters. It clarifies that 'hashes' is pipe-separated or 'all', but it does not explicitly state that 'value' true means force-start and false means un-force-start. The mapping is only implied by the verb phrase, which is insufficient for clear parameter understanding.

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 tool's action: 'Force-start or un-force-start torrents', with a specific verb ('force-start') and resource ('torrents'). It distinguishes itself from sibling tools like resume/pause by using the precise 'force-start' terminology.

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 usage context through its purpose but does not explicitly state when to use this tool versus alternatives such as qbittorrent_torrents_resume or qbittorrent_torrents_set_auto_management. No exclusions or alternative tool references are provided, leaving the agent to infer that force-start is distinct from normal resume.

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