create_material

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states that it creates a material, without mentioning side effects like whether it overwrites an existing material with the same name, whether it requires a selected object, or what the material's initial state is (e.g., unassigned). The parameter descriptions give ranges but do not explain consequences or limitations.

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 and front-loaded with the core purpose, followed by a clean parameter list. Every line adds useful information with no redundancy or fluff, making it efficient for an agent to parse.

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 description covers the basics: what it does and how to set parameters. However, it omits context such as whether the material is automatically assigned to an object, what happens if the name collides, and any return value. Given the tool's simplicity and absence of an output schema, this is acceptable but not fully complete for an agent that needs to decide whether to call it and interpret results.

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 compensates well by explaining each parameter's meaning and format: name as a string, color as an RGBA array in 0-1 range, and metallic/roughness as floats with ranges. This adds value beyond the schema, which only provides types and defaults, making the tool usable without additional lookup.

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 new Principled BSDF material and lists its key parameters (name, color, metallic, roughness). It distinguishes itself from siblings like create_procedural_material by specifying the shader type, making the purpose 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?

No guidance is given on when to use this tool versus alternatives such as create_procedural_material, assign_material, or configure_display_material. The description only states what it does without any context on selection criteria or prerequisites, leaving the agent to infer usage from the tool name alone.

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