uninstall_hda

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

With no annotations, the description carries the full burden of behavioral disclosure. It explicitly warns that the operation has disk and registry side effects and cannot be undone via Houdini undo. This is valuable and goes beyond a generic 'uninstall' statement, though it does not describe return values or error handling.

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 short sentences, front-loaded with the core action and immediately warning about side effects and undo behavior. Every word earns its place; no wasted 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?

The tool is simple (one parameter, no output schema). The description covers purpose, side effects, and undo limitation, which is sufficient for an agent to decide and invoke it. It lacks details like whether confirmation is needed or what happens on failure, but these are not critical for a basic uninstall tool.

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 only one parameter, file_path, with no description. The description does not explicitly explain the parameter, but its meaning is inferable from the tool name and purpose (the HDA to uninstall). Since schema coverage is 0%, the description provides minimal added meaning.

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's purpose: uninstalling an HDA library. The verb '卸载' (uninstall) plus the resource 'HDA 库' is specific and distinguishes it from siblings like hda_install, reload_hda, and update_hda.

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 intended usage is implied by the name and description: use this to uninstall an HDA. However, there is no explicit guidance on when to choose this over alternatives, nor any exclusions or prerequisites. The context is clear but not fully elaborated.

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