Enable or disable a plugin

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

Annotations already indicate a non-readonly, non-idempotent write. The description adds valuable context beyond annotations: the previous state is snapshotted before the write and can be reverted via nuvio_undo, signaling reversibility without contradicting destructiveHint=false.

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 sentences, ~25 words, no fluff. The core action is front-loaded and the snapshot/undo behavior is stated in the second sentence without redundancy.

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?

For a simple toggle with no output schema, the description covers the essential behavior, scope, and reversibility. It doesn't explain return values or prerequisites like whether the plugin must already exist, but the sibling list and tool name imply those. Good enough for an agent to invoke 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 schema has 0% description coverage, so the description must compensate. It maps overall semantics well ('one plugin' → url, 'on or off' → enabled, 'profile' → profile_id), but it doesn't clarify what URL format is expected or that profile_id defaults to 1. It partially compensates but leaves some param-level ambiguity.

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?

States a specific verb ('Turn... on or off') with a clear resource ('one plugin') and scope ('for a profile'). This immediately distinguishes it from siblings like nuvio_toggle_addon and nuvio_add_plugin/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?

Clear context: this toggles an existing plugin's enabled state for a specific profile. It doesn't explicitly exclude add/remove operations, but the plugin/profile framing makes the intended use obvious, and the undo pointer adds practical guidance.

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