qbittorrent_torrents_set_name

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

Annotations already declare this as a write operation (readOnlyHint=false) and non-destructive (destructiveHint=false). The description adds valuable context by explaining that renaming only affects the display name and does not modify files on disk, which is a key behavioral trait not obvious from the tool name alone.

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 that conveys essential information without any fluff. It is front-loaded with the action and immediately provides the key scoping detail about display names versus files.

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?

For a simple 2-parameter tool with annotations and an output schema, the description is highly complete. It states the action, scope, and non-destructive nature. The only minor gap is the implicit 'hash' parameter, but the tool's simplicity keeps this from being a significant omission.

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 provides no descriptions for 'hash' or 'name'. The description clarifies that 'name' is the display name, but 'hash' (presumably the torrent identifier) is left implicit. With 0% schema coverage, the description partially compensates but does not fully explain all parameters.

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 states exactly what the tool does: renames a torrent. The phrase 'display name only, does not touch files on disk' clearly distinguishes this from sibling tools like qbittorrent_torrents_rename_file and qbittorrent_torrents_rename_folder, making its purpose unambiguous.

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 provides clear context: use this tool to change the display name of a torrent without altering underlying files. It implicitly excludes file and folder renaming scenarios by clarifying it does not touch files on disk, though it does not explicitly name alternative tools.

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