material.set_input

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and idempotentHint=true. The description adds useful behavioral context about transaction scope and shared-material confirmation, but it does not explain the optimistic-concurrency expected_* parameters or what destructive actually means in this context. It partially complements the annotations without fully disclosing mutation 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?

Two tightly written sentences with no filler. The core operation is front-loaded, and the shared-material caution is placed at the end. Every word earns its place.

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?

This is a high-complexity tool with 15 parameters, including identity checks, transaction scoping, and idempotency. The description is far too minimal to cover prerequisites, failure semantics, or the purpose of the expected_* fields. An output schema exists, but it does not help explain the required parameters or behavioral constraints.

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 14 parameters are required, so the description must compensate. It only hints at value types (scalar/vector/color) and shared-material confirmation (allow_shared). The many expected_* identity, generation, transaction_id, idempotency_key, node_name, socket_identifier, and material_slot_index parameters are entirely unexplained, leaving an agent unable to populate them correctly from the description alone.

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 uses a specific verb ('Set') and a precise resource ('one exact unlinked, undriven scalar/vector/color material input'), making the tool's function immediately clear. It also scopes the operation to 'inside the active transaction,' which helps distinguish it from related material tools like material.assign or material.texture.bind.

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 conveys clear context: this is for raw, unlinked, undriven inputs and must be used within an active transaction. It also notes that shared materials require explicit confirmation. It does not explicitly name alternatives or give when-not-to-use guidance, but the constraints are reasonably inferable.

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