qbittorrent_search_uninstall_plugin

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

The description says 'Uninstall', which is a destructive/mutating action, but annotations declare destructiveHint=false. This is an annotation contradiction. The description also fails to disclose any consequences (e.g., permanent removal, effect on searches) beyond the contradiction.

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 short sentences that convey the action and parameter format without any wasted words. All information is necessary for basic use.

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 one parameter and an output schema, but the description omits potential edge cases (e.g., nonexistent names, partial failures) and is undermined by the annotation contradiction. It is sufficient for the simplest invocation but not fully complete for an agent encountering errors or needing side-effect awareness.

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 defines 'names' as a string with no format. The description adds critical meaning by specifying that names are pipe-separated, which is essential for correct invocation. This compensates for the schema's 0% coverage.

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 'Uninstall' with the resource 'search plugins', making the action unambiguous. It distinguishes from sibling tools like install_plugin, enable_plugin, and update_plugins by focusing on removal.

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?

Usage context is implied by the tool name and sibling operations, but the description offers no explicit guidance on when to uninstall versus disable or update plugins. It lacks any exclusions or references to alternatives.

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