Install an addon

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

The description adds substantial behavioral context beyond the annotations: it discloses that the existing addon list is read and preserved (append, not replace), and that a snapshot is taken before the write with a revert path via nuvio_undo. This aligns with destructiveHint=false and idempotentHint=false while giving the agent actionable safety information that annotations alone could 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?

Three tight sentences, each earning its place: the first states the core operation, the second discloses the append semantics, and the third covers the snapshot/undo safety net. The most decision-relevant information is front-loaded, with zero wasted 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?

For a write operation with no output schema, the description covers the critical context: what action is performed, how existing state is treated, and how to recover via nuvio_undo. The only gaps are the absence of return-value expectations and undocumented optional parameter details, both minor given the tool's moderate complexity and robust annotations.

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 20%, so the description carries the burden for undocumented parameters. It clarifies the URL's role as the install source and hints that the operation targets a profile (connecting to profile_id), but it does not explain the semantics of name, enabled, or sort_order. The compensation is partial — enough for the required parameter, insufficient for the optional ones.

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 an addon on a profile by manifest URL." It names the installation mechanism (manifest URL), which distinguishes it from sibling tools like nuvio_update_addon, nuvio_toggle_addon, and nuvio_remove_addon. An agent can tell this is the tool for adding a new addon without inspecting other 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 operation context is implied by "Install an addon on a profile" and "only the new addon is appended," which clearly signals this is for adding a new addon rather than modifying existing ones. However, it never explicitly names alternatives or states when NOT to use it (e.g., "to modify an existing addon use nuvio_update_addon"). The usage guidance is clear in context but left to inference.

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