assign_material_workflow

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

With no annotations, the description carries the full burden. It states what the tool does but fails to disclose any behavioral nuances such as whether it creates additional nodes, changes the scene graph, or requires special permissions. The 'workflow' aspect is entirely unexplained.

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 sentence that is concise and front-loaded with the core action. However, it is under-specified, which undermines the value of its brevity, but it does not contain wasteful content.

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 tool's name includes 'workflow' and there is a sibling simply named 'assign_material', the description should explain what the workflow entails. There is no output schema and no annotations, so the description is the only source of context, and it is insufficient to understand the tool's behavior or expected inputs.

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?

The schema has 0% description coverage for parameters, and the tool description provides no additional meaning for 'geo_path' or 'material_path'. Neither the schema properties nor the description explain what these paths refer to (e.g., object paths, asset paths, or node paths).

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 'Assign a material to a geometry node' uses a specific verb and resource, making the basic action clear. However, it does not distinguish this tool from the sibling 'assign_material' or explain the 'workflow' suffix, so it's not fully differentiated.

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?

There is no guidance on when to use this tool versus alternatives like 'assign_material', 'set_material', or 'create_material_workflow'. No context, prerequisites, or exclusions are provided.

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