uninstall_hda

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

No annotations are provided, so the description carries the full burden. 'Uninstall' implies a destructive/mutating action, but the description does not disclose what happens to the HDA, whether it is reversible, or any side effects on the current session. It lacks critical behavioral detail for a destructive operation.

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 brief and to the point, with the main purpose front-loaded. It has no unnecessary prose, but the inclusion of 'ctx' which is not a schema parameter slightly muddies the structure. Still, it is appropriately concise.

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 operation with no annotations and no output schema, the description is incomplete. It does not explain return values, success/failure behavior, whether the current session is affected, or how it differs from related operations. An agent would lack critical information to safely invoke this 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?

Schema description coverage is 0%, so the description must compensate. It only says 'file_path: HDA file path', which adds minimal meaning beyond the schema's type declaration. It does not explain expected format, restrictions, or any other relevant parameter details. The mention of 'ctx' not present in the schema adds confusion.

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 verb 'Uninstall' and the resource 'HDA file from the current session'. It is distinct from sibling tools like install_hda, reload_hda, and create_hda, making its purpose unambiguous.

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 guidance on when to use this tool versus alternatives such as install_hda or reload_hda. It does not mention prerequisites, side effects, or when it is appropriate to uninstall versus other operations, leaving the agent without contextual direction.

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