create_render_node

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

No annotations are provided, so the description carries full burden. It discloses the target location (/out) but says nothing about side effects on the scene, whether the node is automatically connected, required Houdini connection state, error behavior for an invalid renderer, or whether the operation is undoable.

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 short and front-loaded with the core action before the argument list. Each argument line is minimal, though the 'Args:' list is essentially a restatement of schema property names with only the renderer enum adding clear value.

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 mutation tool with no annotations and no output schema, the description is too thin. It omits what the tool returns (e.g., the created node path), whether the operation requires an active Houdini session, and how optional parameters like camera and output_path affect node configuration.

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%, so the description must compensate. It labels all four parameters and provides the accepted renderer values ('karma', 'opengl', etc.), which is useful beyond the bare schema. However, it gives no format details for camera paths, output path syntax, or name defaults.

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 ('Create') and resource ('render (ROP) node') and location ('in /out'). This distinguishes it from generic create_node and from create_lop_node/create_cop_node siblings, though no sibling is named explicitly.

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 like create_node or setup_render. The description only defines the action and arguments, leaving the agent to infer context from the tool name and parameter list.

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