uninstall_hda

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

No annotations exist, so the description carries the full behavioral burden. The phrase 'from the current session' hints that the removal is session-scoped rather than deleting from disk, which is a useful nugget, but there is no disclosure of reversibility, permission requirements, or side effects on dependent nodes. For an uninstall/mutation tool this is a significant gap.

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 one-line purpose is front-loaded and efficient, but the trailing formal 'Args:' block is largely wasted – it documents the non-schema 'ctx' and merely echoes the single parameter name. Tighter without that block.

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?

With no annotations, no output schema, and 0% schema coverage, the description should compensate but does not. It never clarifies the consequence of uninstalling (session-only vs. disk removal), what happens to nodes referencing the HDA, or the expected outcome, leaving the agent under-informed for a destructive-looking operation.

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% and there is one parameter. The description restates 'file_path: HDA file path.', which is essentially a paraphrase of the parameter name and adds no format, path-resolution, or constraint detail beyond the schema. The 'ctx' line documents a field that is not even in the input schema.

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 states a specific verb and resource: 'Uninstall an HDA file from the current session.' An agent can tell it is a removal operation scoped to the session. However, it does not differentiate from closely related siblings like reload_hda, install_hda, or update_hda, so it falls short of a 5.

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?

No when-to-use, when-not-to-use, or alternative guidance is offered. With several sibling tools touching HDAs (reload_hda, install_hda, update_hda, get_hda_info), the description should route the agent, but provides none of this.

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