move_torrent

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

With no annotations, the description carries full burden. It discloses the sequence: stops torrent, optionally moves data (with permission note), points rTorrent, and restarts. This provides good transparency for a mutation tool, though it doesn't mention reversibility or error conditions.

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 sentences, no fluff. The first states the core action; the second details the process. Every sentence adds value, and it is front-loaded.

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 no output schema, the description explains the behavior fully (stop, move, restart). It covers prerequisites (permissions) and the optional data move. Missing return value info, but acceptable for a simple mutation tool.

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 description must compensate. It adds minimal info: 'optionally moves its data' hints at move_data, but hash and directory are not explained beyond the field names. No format or constraint details are given.

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 starts with 'Move a torrent to another download directory,' which clearly states the verb and resource. It distinguishes from sibling tools like start/stop/remove by specifying the move action.

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 when to use (moving a torrent to a new directory) and mentions the prerequisite of rTorrent's execute permission, but lacks explicit guidance on when not to use or alternatives. No exclusions or comparisons to siblings are provided.

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