supervisor_uninstall_addon

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

With no annotations provided, the description carries the full burden. It discloses the destructive nature with 'DANGEROUS' and the required safety flag, but it does not elaborate on consequences such as whether data is permanently deleted or if the operation can be undone.

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 extremely concise with two sentences. Every word serves a purpose: the action, a warning, and a parameter requirement. No unnecessary text.

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 dangerous nature and 0% schema description coverage, the description is minimal. It covers the safety aspect but lacks details on return values, prerequisites, or post-uninstall effects. An output schema exists but is not referenced.

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 must add meaning. It clarifies that confirm must be set to true, which is critical beyond the schema's default of false. However, it does not explain the slug parameter, which is required.

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 'Uninstall an add-on', which is a specific verb+resource. It distinguishes itself from sibling tools like supervisor_install_addon or supervisor_start_addon by focusing on removal.

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 explicitly warns 'DANGEROUS — requires confirm=True', giving a clear guideline that the tool should only be used with the confirm parameter set to true. This effectively prevents accidental misuse, though it does not mention when to use alternatives like stop or disable.

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