load_scene

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

With no annotations, the description carries the full burden of behavioral disclosure. It does not mention side effects such as replacing the current scene, clearing existing data, or requiring an absolute path. Loading is a potentially destructive action, and this description is silent on consequences.

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 a single, focused sentence with no wasted words. It front-loads the action and resource, making it easy to scan.

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 simple one-parameter tool, the description covers only the basic purpose. It lacks usage guidelines and behavioral transparency, making it incomplete for an agent to safely invoke without additional context. The absence of annotations and output schema increases the need for richer description.

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 coverage is 0%, so the description must elaborate on the file_path parameter. It only implies the parameter is the path to a .hip file, but does not clarify whether an empty default is acceptable, what path formats are supported, or how errors like missing files are handled.

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 action ('Load'), the resource type ('.hip file'), and the destination ('into Houdini'). This distinguishes it from sibling tools like save_scene or reload_hda, which involve different operations or file types.

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 is provided on when to use this tool versus alternatives. It does not mention scenarios where loading a .hip file is appropriate, nor does it exclude cases like reloading HDAs or saving scenes.

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