set_file

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

No annotations are present, so the description carries the full burden. It says only that a file parameter is set; it does not state whether existing values are overwritten, what input file formats are valid, whether the node must exist or already be cooked, or what errors occur. For a mutation tool with zero annotation coverage this is thin.

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?

Two compact fragments with the primary action front-loaded and zero filler. The em-dash shorthand and unexplained 'parm' terms make it slightly cryptic, but it is not padded.

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-value explanation is not owed. However, with no annotations and 0% parameter descriptions, the definition leaves the optional parm_name and mutation behavior undocumented; an agent has to guess how to target the right parameter.

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% across all three parameters. The description implies node_path and file_path but never explains the optional parm_name or how it selects the target parameter, leaving a required semantic gap that neither the schema nor the text fills.

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-and-resource pair ('Set a node's file parm'), which is clear to anyone with Houdini domain knowledge, and it explicitly distinguishes itself from import_alembic/import_volume. The term 'parm' is jargon and no output/effect detail is given, but the core purpose 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?

It gives a concrete when-to-use recipe ('create_node + set_file') and names the alternatives NOT to use (import_alembic/import_volume), which is real routing guidance. It stops short of explaining when set_file would be wrong in other cases, but it clearly tells the agent which tools to combine.

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