connect_material_property

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

No annotations are provided, so the description must disclose side effects. It only says 'Connect' without mentioning that this modifies the material asset, may require saving, or whether it overwrites existing connections. This is a mutation tool with zero behavioral disclosure.

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 concise sentence that directly states the purpose with useful property examples. No wasted words, perfectly sized.

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 tool modifies a material asset, but there is no output schema and no annotations. The description doesn't explain return values, side effects, or preconditions. Given the mutation nature, it should at least note the need to save or that existing connections are replaced. Not complete for safe invocation.

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%, with descriptions for all four parameters, so the baseline is 3. The description adds nothing beyond the schema; it only lists example properties that already appear in the enum. No additional semantic value.

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 the action (connect), the entities (an expression and a material output property), and gives concrete examples (BaseColor, Normal, etc.). This distinguishes it from sibling tools like connect_material_expressions, which likely connects expressions to each other.

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 explicit when-to-use or alternatives are provided. The description gives no context about prerequisites (e.g., material must be loaded) or when to prefer this over connect_material_expressions. Usage is only implied by the property list.

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