set_material_instance_base_overrides

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

Annotations already declare destructive=true and idempotent=true, so the bar is lower; the description still adds real context: that changes persist to the asset, that flag+value are set together, and that blend_mode/shading_model may emit warnings. It stops short of describing failure modes or what 'destructive' means for the asset.

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?

Front-loaded with the core action and the key flag/value rule in the first two sentences. The trailing Returns block is long but substitutes for the missing output schema, so it largely earns its space; it could be tightened.

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?

With no output schema, the description usefully enumerates the return fields (applied_count, saved, resolved values, warnings), and it covers persistence and partial-update behavior for a destructive mutation. What is missing is auth/permission expectations and what happens on invalid blend_mode/shading_model input.

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%, so the baseline is 3, but the description adds semantics the schema does not: every provided override implicitly also sets its paired bOverride_ flag, and omission means 'leave untouched' rather than 'clear'. That is genuine meaning beyond the field descriptions.

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?

States a specific verb (Set) plus resource (base property overrides / BasePropertyOverrides) on a precise target (Material Instance Constant). This cleanly distinguishes it from sibling overrides tools like set_material_instance_param_override and get_material_instance_base_overrides.

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 partial-update contract ('each provided axis sets BOTH its bOverride_ flag and value; omitted axes are left untouched') implies when and how to call it, but it never names an alternative or states when NOT to use it (e.g. vs. setting parameter overrides). Usage is inferable, not explicit.

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