load_scene

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

No annotations are provided, so the description carries the full disclosure burden. It does not say whether loading replaces the current scene (and destroys unsaved work), what happens on a missing/invalid path, or whether it blocks. For a scene-level mutation, 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?

One short, front-loaded sentence with zero filler. It is efficient, though the brevity comes at the cost of substance rather than being a virtue of concision.

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 no explanation, but with no annotations, no parameter documentation, and no mention of side effects on the current scene, the definition is not complete enough for an agent to call this destructive operation confidently.

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 file_path parameter has 0% schema description coverage and no explanation in the description. The phrase '.hip file' only vaguely implies the expected path/extension, leaving format (absolute vs relative) and default behavior unstated.

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?

States a specific verb (Load) and resource (.hip file) with the host application named, so the agent knows this opens a Houdini scene. It does not distinguish itself from siblings like lop_import, save_scene, or execute_houdini_code, but the core action is 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 load a .hip versus importing via lop_import or running code, and no prerequisites noted. The agent must infer usage entirely from the name.

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