material_create_preset

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

With no annotations, the description carries the full burden. It mentions optional assignment but does not specify the target object or how assignment occurs. The behavior for empty material_name ('auto if empty') is vague, and there is no information about return values or side effects.

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 extremely concise, using a single sentence plus a structured parameter list. Every sentence is necessary and informative without any redundant information.

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 and no annotations, the description covers the basic action and parameters. However, it lacks details on assignment target, return value, and edge cases (e.g., empty material_name). The tool's output is not described, which is a gap for a create operation.

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 coverage is 0%, so the description's parameter explanations add significant value. Each parameter is described with purpose and constraints (e.g., preset_name references, color_override range). The description compensates well for the lack of schema descriptions.

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 'Create a material from a preset and optionally assign it,' which clearly identifies the action and resource. It distinguishes from sibling tools like material_create_pbr, but does not elaborate on the assignment process, leaving some ambiguity.

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 usage by referencing 'material_list_presets' for preset names, but does not explicitly state when to use this tool versus alternatives like material_create_pbr or material_duplicate. No direct when-not-to-use guidance is provided.

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