ue_create_material

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

With no annotations, the description assumes full burden. It discloses that nodes are actually created and connected (not just a Blueprint abstraction) and mentions the 'auto' key for texture channel inference. However, it does not mention side effects like automatic saving, required editor state, or whether textures must be pre-imported.

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 well-structured with a brief explanation followed by an Args section. It is concise but could be slightly tighter; still, it effectively communicates without waste.

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 tool creates a material but the description does not mention what the function returns (e.g., the asset path). Given no output schema, this is a notable gap. Additionally, it lacks context on prerequisites (e.g., textures must be imported first) or limitations, making it incomplete for the complexity of the operation.

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%, so the description must compensate. It explicitly lists all parameters (package_path, name, textures, scalars, two_sided) and explains each, including the 'auto' key for textures and channel options. This adds significant meaning beyond the bare 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 it creates a material by connecting textures to PBR channels, and explicitly distinguishes from Blueprint graphs by noting full scriptability. This is specific and differentiates from siblings like ue_create_material_instance.

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 explains how to use parameters (textures map, scalars, two_sided) and clarifies the difference from Blueprint graphs. However, it does not explicitly state when to use this tool versus alternatives like creating a material instance or importing presets, so it lacks exclusionary guidance.

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