assign_image_texture

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

Annotations mark this as destructive (destructiveHint: true) and non-read-only, but the description adds no context about what gets modified or potential side effects (e.g., disconnecting existing Base Color connections, creating duplicate nodes). It merely states the additive/connective action without elaborating on the destructive implications.

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 one concise sentence that communicates the core function with no redundant words. It is appropriately sized for a straightforward tool and front-loads the essential action.

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 is minimal and lacks crucial context: it does not mention prerequisites (e.g., material and image must exist), how it interacts with the material's node tree, or whether it replaces existing Base Color connections. The output schema exists, so return values are not needed, but the missing parameter semantics and usage guidance leave the description incomplete.

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%, and the description does not explain any parameters. While parameter names (material_name, image_name, connect) are somewhat self-explanatory, the description does not clarify how they map to the operation, what 'connect' controls, or prerequisites like image existence.

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: 'Add Image Texture node and connect to Base Color' in Indonesian. It specifies the exact operation and target connection, making it easy to understand the tool's purpose. However, it does not differentiate from sibling tools like add_shader_node or create_image_texture, so it loses a point.

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 the tool is used when you want to assign an image texture to a material's Base Color, but it provides no explicit guidance on when to use it versus alternatives (e.g., add_shader_node, connect_shader_nodes, create_image_texture). There are no when-not-to-use conditions or references to sibling tools.

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