qbittorrent_search_install_plugin

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

Annotations already declare readOnly=false and destructive=false, so the agent knows this is a write operation. The description adds the pipe-separated multi-source format but does not disclose side effects such as whether existing plugins are overwritten or if the plugin list needs refreshing. With annotations covering the basic safety profile, this is adequate but not rich.

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 two sentences: the first states the action, the second explains the parameter. It is front-loaded with the purpose and contains no redundant or filler words.

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?

This is a simple single-parameter install tool with output schema available, so the return value is presumably covered elsewhere. The description sufficiently covers the only parameter and the action. Minor missing details like overwrite behavior are non-essential for basic 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 input schema only specifies 'sources' as a string with no description. The description compensates by explaining that sources are 'one or more URLs or file paths separated by a pipe', providing essential format and multiplicity details. This adds significant meaning beyond the bare 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 uses a specific verb 'Install' with a clear resource 'search plugins', which unambiguously identifies the tool's function. It also distinguishes from sibling tools like uninstall, enable, and update through the action 'Install'.

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 when to use it (to add search plugins) but does not explicitly contrast with alternatives such as update_plugins or enable_plugin. No prerequisites, scenarios, or exclusions are mentioned, making the guidance implicit rather than explicit.

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