qbittorrent_sync_torrent_peers

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

Annotations already declare readOnlyHint=true, indicating a safe read operation. The description adds valuable behavioral context about differential updates controlled by rid, which is not captured elsewhere and helps the agent understand the polling pattern.

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 exceptionally concise: two short sentences with the primary purpose front-loaded and no filler. Every word earns its place, making it highly efficient for an agent to parse.

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 has an output schema, so return-value details are covered. However, the description does not clarify the default behavior when rid is omitted (default 0) or contrast it with qbittorrent_sync_maindata, leaving some contextual gaps that could affect correct invocation.

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 explains the rid parameter's role in retrieving changes since the previous reply, but the required hash parameter is only implied as the torrent identifier. With 0% schema description coverage, the description should compensate more for both parameters; it covers rid but leaves hash implicit.

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 tool as providing differential peer data for a single torrent, which distinguishes it from other sync tools. However, it lacks an explicit verb like 'get' or 'fetch', making the action less direct than optimal.

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 that the tool is used for incremental updates by passing the rid from the previous reply, but it does not explicitly state when to use it over alternatives like qbittorrent_sync_maindata or provide any exclusion criteria.

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