material_create_function

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

With no annotations, the description carries the burden of behavioral disclosure. It does well by revealing key side effects: 'Delete/recreate an existing asset at the same path' and 'Save the asset package immediately,' plus exposing the asset to the library. It does not mention failure behavior when overwrite is false, but the core behavioral traits are disclosed.

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 front-loaded with its purpose, uses a compact Args list to add parameter meaning, and includes a helpful example and KB pointer. Every line earns its place without unnecessary elaboration.

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 five parameters with no schema descriptions and no annotations, the description provides a strong baseline: full parameter semantics, side effects, an example, and a KB reference. An output schema exists, so return values need no explanation. Missing usage-guidance and overwrite edge cases are the main gaps.

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%, but the description fully compensates by explaining every parameter: function_name, folder_path, description, overwrite, and save. The example further clarifies invocation syntax.

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 states a specific verb and resource: 'Create a Material Function asset and expose it to the material function library.' This clearly identifies what the tool does and distinguishes it from sibling material-related tools like create_material or material_create_master.

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?

No explicit guidance is given on when to use this tool versus alternatives such as material_create_master, mat_create_material, or material_create_instance_from_master. The KB link is useful but does not provide when/when-not selection criteria.

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