connect_to_material_output

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

Annotations flag destructiveHint=true and readOnlyHint=false, and the description adds real value beyond them: the edit is in-memory with no recompile, no dirty flag, and no save, which tells the agent the change is not persisted until it calls other tools. The one gap is that it never states that wiring into a main input may overwrite/replace an existing connection, which is likely what the destructive hint is warning about.

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?

Front-loaded purpose sentence, then the in-memory constraint, then the sibling alternative, then the return shape. Every sentence carries distinct information and there is no padding.

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?

For a graph-mutation tool the description covers the memory/persistence model, the required follow-up calls, the alternative tool, and even the return shape (compensating for the absent output schema). It is nearly complete; the only omission is the fate of any pre-existing connection on the target input, which matters given the destructive hint.

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 100%, so the schema already documents from_pin, from_node_id, material_path, and output_property in detail. The description's mention of BaseColor/Roughness/Normal and 'one output' adds only marginal meaning over what the schema provides, so the baseline 3 applies.

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?

States a specific verb (wire/connect), the exact source (one output of an expression node), and the exact destination (a main input of a UMaterial asset), with concrete input examples. It explicitly distinguishes itself from the node-to-node sibling connect_material_expressions, so the agent can tell the two apart without opening either schema.

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?

Names the alternative tool and the condition that selects it ('Node-to-node wiring is connect_material_expressions'), and prescribes the required follow-up workflow ('follow with compile_material and save_asset'). Nothing about when to reach for this tool is left to inference.

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