mat_set_property

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description adds useful behavioral context: values are coerced to the target property's type, and the tool sets arbitrary named properties. It does not expand on side effects, but the annotations cover the destructive nature.

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-loaded with the core purpose. The main cost is exact bilingual repetition, which doubles length without adding new information for an agent, but it remains appropriately sized overall.

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 generic setter with 3 parameters and no output schema, the description is complete: it explains what it does, when to use it, that values are converted, and how to avoid invalid property names. Nothing essential 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%, so the schema already documents material, property, and value formats. The description adds meaning beyond the schema by explaining automatic type coercion and emphasizing the need for exact property names, which is important for correct parameter usage.

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 action ('set any named property of a material'), the resource (material), and the type-coercion behavior. It also explicitly frames itself as the fallback for properties without a dedicated tool, distinguishing it from sibling mat_set_* tools.

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 clearly says to use this tool when the property has no dedicated tool, and instructs the agent to check the exact property name with get_class_properties first. This gives direct decision-making guidance relative to alternatives.

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