production.material_validate_udim

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

The annotations declare readOnlyHint=true, but the description explicitly says apply=true writes candidate materials. That is a direct contradiction of the declared safety profile, so behavioral transparency cannot be trusted even though the description also says original slots, images, UVs, geometry, and animation remain unchanged.

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 compact and front-loads the default versus apply behavior, which is helpful. However, it becomes a dense list of vague workflow requirements such as 'material plan references for lifecycle calls' and 'technical QA' without concrete structure.

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 seven-parameter tool with no schema descriptions, the definition is incomplete: it explains almost none of the inputs and contradicts its readOnly annotation. The presence of an output schema means return values need not be described, but that does not compensate for missing parameter guidance and unsafe write ambiguity.

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 seven parameters, and the description only explains apply=true / default behavior. It hints at profiles and material plan references, but gives no meaning for options, definition, material, object_name, or material_name, leaving most invocation choices undocumented.

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 implies inspection/proposal validation of UDIM materials and states that apply=true writes only owned candidate materials. However, it does not clearly define what UDIM validation actually checks, and it does not distinguish this from sibling tools such as material_validate_uv, udim_plan, or udim_apply_plan.

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?

It gives a default mode (inspect or propose) and a conditional write mode (apply=true), plus prerequisites like technical QA and visual review before acceptance. That is useful context, but it never names alternatives or states when this tool should not be used instead of related UDIM/material validation tools.

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