material_from_texture_folder

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

No annotations are provided, so the description must carry the full behavioral burden. It communicates that it creates a PBR material, but it does not disclose side effects such as node creation, whether the material is assigned to an object via assign_to, what happens to an existing material with the same name, or failure behavior. This is insufficient transparency for a mutating 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 compact sentence with no filler and front-loads the main action (scan folder). It is appropriately short, though its brevity contributes to the missing parameter and behavioral detail.

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 three parameters with no schema descriptions, no output schema, and no annotations, this description is too thin. It does not explain what 'name' and 'assign_to' do, what the tool returns, or how the created material is exposed, so an agent cannot fully predict invocation consequences.

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 is the only place where parameter meaning can be explained. It adds meaningful context for 'folder' by specifying the required filename patterns, but it gives no explanation of the optional 'name' or 'assign_to' parameters, leaving two of three parameters essentially unexplained.

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 names a specific verb (scan/recognize/create), a resource (texture folder), and an outcome (PBR material), and the 'from_texture_folder' scope separates it from generic material tools like create_pbr_material. It lacks an explicit contrast with sibling tools, so it doesn't earn a 5.

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 intended context—when you have a folder of basecolor/roughness/metallic/normal/height/ao image files—is implied by the description, but there is no explicit when-to-use, precondition, or guidance about when to choose this over create_material/create_pbr_material/assign_material. Thus usage guidance is present only at the level of implication.

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