production.material_create_handoff

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

Annotations already declare destructiveHint=false and readOnlyHint=false, and the description adds meaningful context: the default is non-writing, apply=true is the write path, writes are limited to 'owned candidate materials,' and originals (slots, images, UVs, geometry, animation) remain unchanged. This clarifies the safety profile well beyond the annotations, though it omits authentication or rate-limit context.

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 brief, but the second sentence is a dense run-on list mixing input guidance with process recommendations (technical QA, controlled lighting, visual review). It is front-loaded with the tool name and default behavior, yet the overall structure could be cleaner and more scannable.

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 complex tool with eight optional parameters, zero schema descriptions, and an output schema. The description covers default/apply behavior and preservation guarantees but says almost nothing about how to supply the definition, options, material, profile, or operation identifiers. For an agent to invoke it correctly without schema descriptions, substantially more parameter context is needed.

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% across eight parameters, so the description must carry the full semantic burden. It only explains the apply parameter explicitly; the roles of options, profile, material, definition, object_name, operation_id, and material_name remain undocumented. 'Material plan references' and 'explicit channels/profiles' hint at some parameters but do not map them clearly.

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 says the tool will 'inspect or propose by default' and that 'apply=true writes only owned candidate materials,' which gives some concrete behavior. However, the term 'handoff' is never explained, and there is no differentiation from sibling tools like material_create_candidate or material_apply_candidate. An agent can infer that this is a material creation planning/handoff step but cannot confidently tell what unique resource it operates on.

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 gives a default mode (inspect/propose) and an explicit apply=true condition, and it points toward lifecycle calls using material plan references. It also mentions QA, controlled lighting, and visual review before acceptance. However, it does not name any alternative tools or state when not to use this tool, leaving tool selection largely implied.

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