set_material_3d

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

No annotations are provided, so the description must carry behavioral disclosure. It only says 'Create and apply', but does not explain what happens if the material already exists, whether it creates a new resource or modifies an existing one, or any side effects (e.g., overriding existing material). This is insufficient for a mutation operation.

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 sentence that is front-loaded and efficient. Every word contributes to understanding the tool's core function 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 the moderate complexity (2 parameters, nested object, no output schema), the description is adequate but minimal. It explains the main function but lacks details on return values (e.g., whether it returns the created material path or a success status) and error conditions (e.g., invalid path). With no output schema, some additional context would be beneficial.

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 100%; both parameters have descriptions. The tool description adds the context that the material type can be StandardMaterial3D or ShaderMaterial, which goes beyond the schema property description of 'Material properties'. However, it does not elaborate on the structure of the 'properties' object beyond listing a few example keys.

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 action ('Create and apply') and the resource ('StandardMaterial3D or ShaderMaterial') to a specific target ('mesh'). It distinguishes from siblings like 'assign_shader_material' and 'set_shader_param' by specifying the creation and application aspects.

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 (e.g., 'assign_shader_material', 'set_shader_param'). It does not mention prerequisites, contexts, or situations where this tool is preferred, leaving the agent to infer usage.

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