reload_hda

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

With no annotations, the description carries the full burden, yet it says nothing about side effects: whether existing HDA instances are refreshed or invalidated, whether unsaved node-level overrides are lost, or what permissions/state are required. 'Reload from disk' implies mutation of in-memory state, but none of this is disclosed.

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?

Front-loaded with the core action in one short sentence, followed by a minimal Args block. The 'ctx: MCP context' entry is noise (it is not a schema parameter), but overall there is no padding.

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 state-mutating tool with no annotations, no output schema, and an undocumented parameter, the description omits what an agent needs: side effects on live nodes, error behavior for a missing/invalid file, and any precondition. It is adequate only as a label, not as operating instructions.

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 parameter has 0% schema description coverage, so the description must compensate. It only restates the name with 'HDA file path' — no format, expected file type (.hda/.otl), path resolution rules, or whether a relative/absolute path is needed.

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 gives a specific verb ('Reload') and resource ('HDA file') plus the source ('from disk'), which clearly separates it from unrelated siblings. However, it does not distinguish itself from close siblings like install_hda, update_hda, or reload_plugin, so an agent comparing those must infer the difference.

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 reload versus reinstall (install_hda), update (update_hda), or reload a plugin (reload_plugin). The narrow sibling set makes this a real gap, since 'reload' could plausibly be confused with those operations.

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