create_node

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does not state that this is a write operation, whether it modifies the scene destructively, what happens on failure, or whether it can be undone. The prerequisite call is helpful but is usage guidance, not a behavioral trait of the tool itself.

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 front-loaded with the core action, followed by a useful prerequisite note and parameter list. The middle paragraph about Houdini's thousands of nodes is somewhat tangential but still relevant guidance, and the overall structure is 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?

Given the absence of annotations and an output schema, the description covers the basic purpose, a key prerequisite, and parameter meanings. It omits important context such as return values, error conditions, and side effects, which are necessary for safe invocation of a node-creation tool in a complex scene graph.

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 lists all four parameters and gives brief meanings (e.g., 'Parent network path', 'Node type (e.g. geo, box, grid)', '[x, y] network editor position'), which adds some value. However, it does not clarify path formatting, optionality, or defaults, so the compensation is only partial.

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 states a specific verb and resource: 'Create a node inside a parent network.' This is clear and direct, but it does not distinguish this tool from sibling creation tools like create_lop_node, create_cop_node, or create_chop_node, which all create nodes in different contexts.

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 clear context by recommending a prerequisite call to list_node_types and explains why dedicated nodes are preferable to VEX or Python. However, it does not provide explicit exclusions or compare this tool against other node-creation siblings, leaving an agent to infer when to use create_node versus create_lop_node etc.

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