kernel_extensions_uninstall

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

With no annotations, the description carries the full behavioral burden, and it does disclose the critical fact that removal deletes both files and the database row, implying irreversibility. It says nothing about permission requirements, whether an in-use extension blocks removal, or whether any confirmation is required.

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?

One short sentence with zero filler, and the destructive scope is front-loaded in the parenthetical. It is efficient, though the brevity edges toward under-specification rather than optimal density.

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 mutation with no annotations and no output schema, the definition should cover prerequisites, irreversibility, and the identifier source. Only the deletion scope is covered, leaving an agent without enough to call it safely and 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 single required parameter has 0% schema description coverage and the description never mentions it. It is unclear whether "id" is an extension identifier, slug, or display name, and whether it can be obtained from kernel_extensions_list.

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?

"Remove an extension" gives a specific verb and resource, and the parenthetical clarifies the scope of removal (files + row). It does not distinguish this from sibling uninstall tools such as kernel_marketplace_uninstall or kernel_marketplace_catalog_uninstall, so an agent must infer which uninstall target applies.

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?

There is no when-to-use guidance, no exclusions, and no stated prerequisites (e.g., whether the extension must be disabled first, or how this differs from the marketplace uninstall variants). The agent gets no routing signal beyond the name.

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