supervisor_install_addon

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

With no annotations, the description carries the full burden. It only states the prerequisite and action, but does not disclose key behavioral traits such as whether installation restarts services, if it is async or sync, error handling, or idempotency. This is minimal disclosure for a mutation tool.

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 a single 11-word sentence that is front-loaded and efficient. No redundant information.

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?

Given the tool's complexity (one parameter, many siblings, no annotations), the description is incomplete. It does not explain the output, installation behavior, or how it differs from similar tools like supervisor_update_addon. The prerequisite is mentioned but could be expanded.

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 for the single parameter 'slug'. The description says 'from its slug' but does not explain what a slug is or how to obtain it. It adds some context (prerequisite about repository) but does not compensate for the lack of schema description.

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 clearly states the tool installs an add-on using its slug, with a prerequisite that it must be in a registered repository. This clearly distinguishes it from sibling tools like supervisor_uninstall_addon or supervisor_update_addon.

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 (to install an addon) and mentions a prerequisite but does not provide explicit guidance on when not to use it or how it differs from related tools like supervisor_start_addon or supervisor_update_addon. No alternatives are given.

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