reload_hda

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

No annotations are provided, so the description must carry the burden of disclosing behavior. It only says 'Reload an HDA file from disk' and mentions the file_path argument. It does not mention what happens to existing node instances, whether the reload is synchronous, or if any side effects occur. The behavior is under-specified.

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 very short and to the point, with no filler. It is appropriately sized, but it omits important details; however, conciseness is not the issue here, so a 4 is warranted.

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 the tool reloads an HDA file and has no output schema or annotations, an agent needs more context: what does 'reload' do to the current scene, are there side effects, how does this differ from install/update, and does it require the HDA to be already installed? The description is too minimal to fully guide correct invocation.

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 the description only lists the parameter name 'file_path' without adding any semantics beyond the schema's bare property. The description also mentions 'ctx: MCP context' which is not in the schema, but provides no explanation of how it is used. The parameter is under-documented.

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 the tool reloads an HDA file from disk, which is a clear verb-resource pair. However, it does not distinguish this from sibling tools like install_hda, update_hda, or create_hda, which an agent might confuse with reloading. The purpose is understandable but not unique among siblings.

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 guidance on when to use this tool versus alternatives. It does not mention that reload is for updating an already-installed HDA after external changes, nor does it compare with install_hda or update_hda. The context of 'reload' implies an existing HDA, but this is left to the agent to infer.

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