blender_iso_apply_npr_material

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It indicates a mutating action, but does not disclose whether existing materials are replaced, whether node groups are created, whether the operation is reversible, or what happens to the target object's current shading.

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, front-loaded sentence with no filler or repetition. It is efficient, though the brevity comes at the cost of substantive guidance that is penalized in other dimensions.

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?

With six parameters, no annotations, and no output schema, this description is too thin to fully guide correct invocation. It omits workflow context, material replacement behavior, expected results, and any details about how parameters interact.

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%, yet the description provides no explanation of the six parameters. It does not clarify what 'palette', 'pixelSnap', 'outlineWidth', 'shadingSteps', or 'smoothNormals' mean in context, leaving the agent to rely entirely on names and 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?

The description uses a specific verb ('Applies') and concrete effect ('stylized non-photorealistic pixel/toon shading and palette quantization') on a clear resource ('objects'). It is clearly distinct from the sibling tools, though it does not explicitly name or contrast any alternative.

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 apply this material versus using the other Blender ISO tools, no mention of workflow prerequisites, and no exclusions. The agent must infer usage entirely from the tool name and description.

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