get_material_instance_base_overrides

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuine semantic value beyond that: the bOverride_ flag semantics (a false override means the parent's setting wins regardless of the stored value) and the surface-level rendering role of these settings.

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-loads the core purpose and the enumerated fields, then adds the flag-semantics warning and the Returns block. Slightly long but each sentence contributes; the Returns block is justified since no output schema exists.

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 single-parameter read tool with no output schema, the description supplies the returned field structure, the override-flag semantics, and the diagnostic context. Nothing an agent needs to call and interpret it correctly is missing.

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% and the single material_instance_path parameter is documented as a content path to a UMaterialInstanceConstant. The description adds no additional parameter-level detail (format, resolution behavior), so the baseline of 3 applies.

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 (Read) and resource (a material instance's base property overrides) and enumerates exactly what is returned: blend mode, two-sided, shading model, opacity mask clip value. It is clearly distinguishable from the parameter-oriented siblings (get_material_instance_params) and names its writer counterpart.

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?

Provides strong contextual guidance: it flags these as separate from parameters and notes that a material that looks wrong despite correct parameters is often a blend-mode override, effectively telling the agent when to reach for this tool. It names set_material_instance_base_overrides as the writer, but offers no explicit when-not or alternative read tool comparison.

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