move_torrent_data

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

Annotations already indicate idempotence and non-read-only behavior. The description adds useful behavioral detail by distinguishing between physically moving files and only updating the recorded path. It does not cover edge cases like destination conflicts or permissions, but that is acceptable given the annotation coverage.

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 compact and well-structured: a two-sentence overview followed by a focused Args list. Every sentence adds value, and there is no filler or repetition of schema fields.

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 annotations, an output schema, and a parameter-by-parameter description, the essential information for invoking the tool correctly is present. Minor gaps like destination-directory creation or cross-filesystem behavior are not mentioned, but they are not required for basic correct use.

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?

The schema has 0% description coverage, but the description compensates fully by explaining all three parameters: ids as torrent IDs or hash strings, location as the target directory, and move with its true/false semantics. This is exactly the kind of parameter-level clarity agents need.

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 identifies the action ('Move') and the resource ('a torrent's data'), and it explains the dual behavior: physically moving files or updating the recorded path. It does not explicitly differentiate from sibling tools like rename_torrent_path, so it is clear but not fully sibling-aware.

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 gives practical guidance for both modes: move=True moves existing files, while move=False is for data the user already moved. It does not explicitly mention when to prefer this tool over alternatives, but the mode-level usage context is strong.

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