clear_material_parameter_overrides

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is present. The description adds value beyond the annotations by specifying exactly what is reset (scalar, vector, and texture overrides) and where the replacement defaults come from (the parent material).

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 front-loaded with the action and resource, then adds the precise effect in one short clause. The return shape line is compact and useful, and no sentence is wasted.

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?

The tool has low complexity, a fully documented required parameter, and rich annotations covering safety. The only missing structured element is an output schema, and the description compensates by stating the exact return shape, so an agent has everything needed to invoke it correctly.

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 100% and the single parameter 'material_instance_path' is already documented as the content path to the MIC. The prose does not add syntax, format, or behavioral detail for that parameter, so the baseline score 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?

The description states a specific verb and resource: 'Clear all parameter overrides on a Material Instance Constant.' It also bounds the scope by naming scalar, vector, and texture parameters, so an agent can distinguish this from override setters and from collection-clearing siblings without opening the schema.

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?

Usage is implied by the effect statement: it resets parameter values to defaults inherited from the parent material. However, the description never states when to choose this tool over alternatives such as clear_mpci_parameter_overrides or set_material_instance_param_override, and it gives no prerequisites or exclusions.

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