Load hip

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known from structured data. The description adds only 'into the current session', which faintly implies replacement of existing state but never states that unsaved work is discarded or what happens to open nodes. For a destructive load operation it should warn about loss of the current scene.

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?

One short, front-loaded sentence with zero filler. It is efficient, though its brevity is partly under-specification rather than pure economy.

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?

An output schema exists, so return values need not be described. However, for a destructive one-parameter tool with no schema documentation and sibling tools that can also mutate the session, the description omits the two things an agent most needs: the path format and the destruction of current session state.

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%: the single 'path' parameter has no type detail, format, or example in either the schema or the description. The description does not compensate by saying whether the path is absolute, relative to $HIP, or whether a .hip/.hipnc extension is required, so the agent has to guess at the most important input.

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 names a specific verb and resource ('Load a hip file') plus the target ('the current Houdini session'), which distinguishes it reasonably well from the sibling save_hip. It stops short of anything an agent couldn't already infer from the name and title, so it sits just below 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?

There is no guidance on when to call this versus alternatives such as execute_python or rebuilding a scene via create_node, and no mention of prerequisites like saving current work first. The agent is left to infer all timing and precondition decisions.

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