material_create_instance_from_master

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

With no annotations provided, the description carries the behavioral disclosure burden. It discloses the destructive overwrite behavior ('Delete/recreate an existing asset at the same path') and the save side effect ('Save the asset package immediately'). This is meaningful transparency beyond the bare schema, though it does not mention failure behavior or validation rules.

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 compact and well-structured: a one-sentence purpose, a terse Args list, a KB pointer, and a concrete example. Every part adds value, and the example clarifies the expected path format.

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 an output schema exists and the description covers all parameters plus the important destructive and save side effects, nothing essential is missing for an agent to invoke this tool correctly. The KB link provides an additional path to deeper material context if needed.

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 fully compensates. The Args block gives meaningful semantics for all five parameters: naming example, parent material or material instance path, Content Browser folder, overwrite behavior, and save behavior. This is complete and goes well beyond the raw 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 opens with a specific verb and resource: 'Create a Material Instance Constant from a master Material.' This clearly identifies the asset type being created and the input resource. However, it does not explicitly contrast with nearby sibling tools like create_dynamic_material_instance or material_create_master, so it lacks explicit sibling differentiation.

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 implies the usage context through 'from a master Material' and by naming the instance asset parameters, but it never states when to prefer this tool over alternatives. No exclusions or alternative routing guidance is provided, only a KB reference. This is reasonable but leaves the when-to-use decision mostly to inference.

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