uninstall_extension

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

No annotations are provided, so the description carries full burden. It mentions the WebDriver BiDi command and ID requirement but omits behavioral details such as error handling, idempotency, permissions required, or side effects of uninstallation.

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 sentences long, front-loading the action and technology, then providing necessary context about the ID. No redundant or unnecessary 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 no annotations and no output schema, the description covers the core action and input source adequately. However, it lacks details on return value, error conditions, and side effects, which a moderate-complexity tool might require.

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 describes the parameter 'id' as 'Extension ID', and the description adds value by specifying the source (install_extension or list_extensions). This goes beyond the schema's basic definition.

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 action ('Uninstall a Firefox extension') and the specific technology used ('WebDriver BiDi webExtension.uninstall command'). It distinguishes from sibling tools like install_extension by focusing on the opposite operation.

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 provides explicit guidance on how to obtain the required extension ID, referencing install_extension and list_extensions. It does not explicitly state when not to use the tool, but the context is clear given no alternative uninstall methods exist.

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