Remove an addon

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

The annotations already declare destructiveHint=true, but the description adds useful behavior beyond that: the previous state is snapshotted before the write and can be reverted via nuvio_undo. This gives the agent important information about recoverability that the annotations alone do 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 two tight sentences with no filler. The action verb is front-loaded, and the snapshot/undo note is valuable, compact context that earns its place.

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 destructive operation with four parameters and no output schema, the description covers the core action and undo safety but omits identifying-parameter semantics. The schema's confirm description helps, but the combination of id/url ambiguity and the absence of required-parameter guidance leaves the definition only minimally viable.

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 only 25%, with only 'confirm' documented in the schema. The description adds little parameter-level meaning: 'from a profile' hints at profile_id, but it does not explain how to identify the addon via 'id' versus 'url', whether one is required, or how profile_id is used. This is a meaningful gap for a tool with four undocumented parameters.

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') and names the resource ('one addon from a profile'), making the operation unmistakable. It distinguishes itself from sibling tools like nuvio_add_addon, nuvio_toggle_addon, and nuvio_update_addon without needing to open their schemas.

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 this is the tool for permanently removing an addon and mentions the undo path, but it does not explicitly state when to choose this over nuvio_toggle_addon or nuvio_remove_plugin. The usage context is inferable but not spelled out with alternative exclusions.

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