material.texture.bind

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

Annotations already declare destructive and idempotent behavior, so the description mainly adds context beyond them. The statement that 'existing links require an exact replacement guard' warns about replacement behavior and implies that pre-existing connections are affected. It does not fully explain what gets destroyed, but combined with destructiveHint=true this is reasonably transparent.

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 short sentences, no filler, key action front-loaded. The first sentence states the operation and target, and the second adds an important constraint. Every word earns its place despite some jargon.

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 complex 17-parameter, 12-required-parameter tool with concurrency guards and identity expectations, this description is far too thin. It gives no guidance on how expected_* identities work, what transaction_id/idempotency_key are for, what mapping or coordinates mean, or when allow_shared/replace_existing should be true. The output schema exists, but the description still leaves an agent guessing about most required inputs.

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%, so the description must compensate for 17 parameters and 12 required fields. It provides only broad hints: 'exact local image' maps to image identity parameters, 'Principled PBR channel' maps to channel, and 'replacement guard' hints at expected_link_identities/replace_existing. Most parameters—transaction_id, all expected_* fields, idempotency_key, mapping, coordinates, allow_shared—remain unexplained.

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 ('Bind') and identifies the resource and destination: 'one exact local image' through 'semantic mapping nodes' to a 'Principled PBR channel.' This makes the tool's core function understandable and distinguishes it from generic material setters. However, the phrase 'generated semantic mapping nodes' is jargon and does not clearly separate it from sibling tools like material.set_input or material.texture.clear.

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?

There is no explicit statement about when to use this tool versus alternatives, and no named sibling or exclusion condition. The line 'Existing links require an exact replacement guard' hints at a precondition but does not tell an agent when this tool is appropriate or when to choose material.texture.clear or material.set_input instead.

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