create_shader_node

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It only states that a node is created, implying mutation, but does not mention side effects, whether the material must exist, if the operation is reversible, or what the output contains. This is a significant gap for a creation tool.

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 is immediately clear what the tool does, and the core action is front-loaded. This is appropriately concise.

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?

Despite having an output schema, the description omits essential context: it doesn't mention that the material must already exist, what node types are valid, or how the location parameter is interpreted. For a tool with three parameters and no annotations, this level of detail is insufficient for correct invocation.

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%, meaning the schema provides no parameter descriptions. The description only hints that material_name identifies the material, but it does not explain node_type values or the location format, leaving the agent without enough information to set parameters correctly. The description fails to compensate for the schema's lack of coverage.

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 (create) and resource (shader node) scoped to the material's node tree. This clearly distinguishes it from siblings like connect_shader_nodes, delete_shader_node, or get_shader_node_tree, so the agent can tell them apart without opening the schema.

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 such as add_image_texture_node, create_emission_material, or create_material. There is no mention of prerequisites (e.g., material must exist) or exclusions, leaving the agent without enough context to choose correctly.

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