Install a plugin

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

Annotations already signal a mutating, non-destructive operation, and the description adds genuinely useful behavior beyond that: it preserves the existing plugin list and snapshots the previous state before the write, with nuvio_undo as the revert mechanism. This is a strong behavioral contract for a write operation.

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 short sentences, no filler, and the most important facts are front-loaded: what the tool installs, what it preserves, and how to undo it. Every sentence adds operational value.

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 adequate for the straightforward url-plus-profile call, and the snapshot/undo detail adds meaningful context. It falls short of complete coverage, however, because several optional parameters are unexplained, the failure behavior is not mentioned, and there is no output schema to clarify what the tool returns.

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?

Schema description coverage is 0%, so the description carries the burden of explaining the parameters, but it only clarifies the URL and profile intent, and even that is implicit. The name, enabled, and repo_type parameters are not explained at all, leaving gaps for agents trying to use the full tool correctly.

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 a specific verb and resource: install a plugin on a profile by URL, while also noting the existing plugin list is preserved. This distinguishes it clearly from sibling actions like nuvio_toggle_plugin, nuvio_reorder_plugins, and nuvio_remove_plugin.

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: when installing a plugin by URL. It also gives an explicit recovery path via nuvio_undo, but it never states when not to use the tool or which sibling alternatives are better for enabling, reordering, or removing plugins. The agent has to infer that from the sibling tool names.

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