set_material

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

No annotations exist, so the description bears full responsibility for behavioral disclosure. It mentions 'create or apply' implying mutation, but doesn't explain whether it overwrites existing materials, creates new nodes, requires specific permissions, or what the side effects are. This is insufficient for a mutation tool.

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 a single concise sentence with no fluff. However, it is so underspecified that it sacrifices necessary detail for brevity. It earns a middle score because while it is efficient, it omits critical context that could be added without bloating.

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 4 parameters, 0% schema description coverage, no output schema, and no annotations, the description is far from complete. It doesn't explain material types, parameter object structure, or the distinction between creating vs applying. It covers only the most basic action, leaving the agent unable to correctly set up arguments.

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 description provides zero parameter information beyond the schema's bare names. With schema description coverage at 0%, the description was the only chance to explain what 'parameters', 'material_type', or 'name' mean, but it fails to do so. Users are left completely in the dark.

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?

Description uses specific action verbs ('create or apply') and targets a specific resource ('material to an OBJ node'). While the double verb is slightly ambiguous, it does convey the core function and distinguishes from siblings like assign_material or create_material_network by specifying the OBJ node context.

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 on when to use this tool versus alternatives. There are many related sibling tools (assign_material, create_material_network, create_material_workflow) but no comparison or exclusion criteria provided. The description only states what it does, not when to choose it.

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