add_shader_node

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

The description explains the function and return value but does not disclose potential side effects, error conditions, or prerequisites (e.g., material must exist). With no annotations, the burden is on the description, and it partially meets it.

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 concise docstring with clear purpose, Args, and Returns sections. It is front-loaded and every sentence adds 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?

The description covers input parameters and return value, and there is an output schema. However, it does not mention prerequisites or connection to sibling tools, leaving minor gaps for an agent.

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%, but the description fully explains each parameter in the Args section, including type, default, and an example for node_type. This adds substantial meaning beyond the schema.

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 'Add a shader node to a material's node tree,' specifying the verb (add), resource (shader node), and target (material's node tree). This distinguishes it from siblings like add_geometry_node or add_texture_node.

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?

The description does not provide guidance on when to use this tool versus alternatives like connect_shader_nodes or set_material_property. It lacks explicit context for usage scenarios or prerequisites.

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