assign_shader_material

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

No annotations. Description only states creation and assignment but omits side effects (e.g., overwrites existing material), return value, or required permissions. For a mutation tool, this is insufficient.

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?

Single sentence, no wasted words. Front-loaded with verb and resource. Appropriate length for a simple tool.

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?

No output schema and no annotations; description fails to explain what happens after assignment (e.g., does it return success/failure? Does it open editor?). Lacks completeness for a mutation tool with two parameters.

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 covers 100% of parameters with descriptions. Description adds no extra meaning beyond what the schema already provides. Baseline 3 is appropriate.

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?

Clearly states it creates a ShaderMaterial and assigns it to a node's material property. Distinguishes from sibling tools like set_material_3d which sets an existing material, or create_shader which only creates the shader.

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?

Implied usage: when you need a new ShaderMaterial assigned to a node. No explicit when-not-to-use or alternatives. Agents might confuse with set_material_3d or assign_shader_param. Could benefit from mentioning prerequisites or that it overwrites existing materials.

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