ue_create_material_instance

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

No annotations are provided, so the description carries full burden. It discloses that instancing does not recompile the shader graph, a key behavioral trait. However, it lacks details on side effects, authorization needs, or error handling.

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 concise, with purpose and benefit front-loaded, followed by parameter details. It is not verbose but could better separate general description from parameter listing.

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 no output schema or annotations, the description should include return behavior or post-creation effects. It does not mention what the tool returns or whether the instance is automatically saved. Adequate but incomplete.

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?

With 0% schema coverage, the description compensates by listing each parameter with its purpose and value types (scalar, color, bool, texture). This adds significant meaning beyond the bare schema, though exact formats for complex types could be more precise.

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 the tool creates a material instance from a parent material and sets parameters, using specific verb and resource. It distinguishes from sibling tools like ue_create_material by emphasizing that instancing avoids shader recompilation.

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 when to use (for multiple variants without recompilation) but does not explicitly state when not to use or name alternative tools. However, context implies alternatives like ue_create_material for new materials.

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