qbittorrent_app_default_save_path

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

The annotations already provide readOnlyHint=true, so the safety profile is covered. The description adds useful context beyond that: it specifies that this is the default path for new torrents (not existing ones) and provides an example path format (Windows absolute path). This is valuable behavioral context that the annotation does not convey.

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 phrase that communicates the tool's purpose with an example. There is no redundant wording or filler. For a tool this simple, the extreme brevity is appropriate and effective.

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 the zero-parameter scope, the read-only annotation, and the presence of an output schema, the description is fully complete. It covers what the tool returns (the default save path) and the relevant nuance (for new torrents). No additional context is necessary for an agent to use this tool correctly.

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 tool has zero parameters and the schema is empty, so the baseline is 4. The description correctly adds no parameter information, and none is needed. The description implies this is a simple getter with no inputs, which aligns with the schema.

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 exposing the default save path for new torrents, with a concrete example. This is a specific resource (app default save path) and is distinct from sibling tools like app_get_preferences, which are more general. The meaning is immediately clear despite lacking an explicit verb.

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?

There is no explicit guidance on when to use this tool versus alternatives. The usage is implied by the tool's specific scope and name; the agent can infer that this is the appropriate tool for retrieving the default save path. However, no exclusions or alternative recommendations are provided.

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