qbittorrent_torrents_add_trackers

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

Annotations indicate readOnlyHint=false and destructiveHint=false, but the description adds little beyond the operation itself. It mentions the URL format (newline-separated), but does not disclose whether existing trackers are preserved, duplicates are handled, or what side effects occur.

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 concise sentences with no filler. The purpose is front-loaded, and the additional sentence about URL formatting is necessary and immediately useful.

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 simple with two parameters and an output schema exists, so return details are not needed. The description covers the core usage and the critical URL parameter format, but could note that the operation appends to existing trackers for full clarity.

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 description explicitly defines the 'urls' parameter format ('separated by newlines'), which is critical since the schema has no descriptions. The 'hash' parameter is not explained but is self-evident from the context of adding trackers to a torrent.

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: 'Add trackers to a torrent.' This is a specific verb and resource, and it clearly distinguishes from sibling tools like 'edit_tracker' and 'remove_trackers' by the verb 'add'.

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?

No guidance is provided on when to use this tool vs alternatives (e.g., edit_tracker or remove_trackers). It doesn't mention prerequisites, such as the torrent existing or that this appends to existing trackers rather than replacing them.

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