start_torrents

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

Annotations already mark the tool idempotent and non-destructive; the description adds the queue-respecting behavior and the all-torrents default when ids are omitted. It does not go into error or side-effect detail, but the annotation coverage lowers the burden.

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 short sentences plus a one-line Args entry; no filler, and the key distinction is front-loaded. It is appropriately sized for a one-parameter tool.

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 a simple optional single parameter and an output schema, the description supplies the needed call semantics. The only notable omission is an explicit pointer to the now-start sibling, which keeps it slightly below excellent.

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 coverage is 0%, so the description bears the full load; it explains that ids are torrent ids or hash strings and that omission targets every torrent. This resolves the schema's bare anyOf and default null.

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 the specific action 'Start torrents' and the qualifier 'respecting the download queue,' which differentiates it from sibling start_torrents_now. The resource and behavior are immediately clear.

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?

It states the only decision point for ids ('Omit to start every torrent') and implicitly frames this as the queue-respecting variant. It does not explicitly name start_torrents_now as the alternative, so exclusion guidance is only inferred.

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