create_material

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

The description discloses critical behavior: returns error if asset exists, force=true deletes and recreates. It also lists all parameters with allowed values. Since no annotations are provided, the description carries the full burden and covers safety and mutation well.

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 the main purpose and error behavior. The Args section is well-structured but slightly lengthy. Every sentence adds value, though some parameter descriptions could be more concise.

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 the presence of an output schema (not shown but indicated), the description doesn't need to detail return values. It covers creation, error handling, and all parameters. For a material creation tool in a game engine context, it is complete.

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?

The schema has 0% description coverage, but the tool's description provides detailed explanations for all 7 parameters, including default values and valid options (e.g., blend_mode enum values). This adds significant value beyond the schema's type-only definitions.

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 new Material asset, distinguishing it from sibling tools like create_material_instance. The verb 'Create' and resource 'Material asset' are specific and unambiguous.

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 the force parameter (to delete and recreate if asset already exists) and implies when not to (to avoid overwriting the editor popup). However, it does not explicitly compare to sibling tools or specify prerequisites.

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