set_material_property

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

No annotations are provided, so the description must carry the full burden. It states the action and return type but does not disclose side effects, failure modes (e.g., if material lacks a BSDF node), permissions, or whether the node is created if missing.

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 well-structured with a clear first sentence and an Args/Returns format. It is concise at 8 lines, though the Args section partially repeats schema field names while adding value descriptions.

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 description covers core functionality but omits prerequisites (e.g., material must exist and have a BSDF node) and error behavior. The return type is vaguely described as a 'confirmation dict,' which is minimal despite an output schema existing.

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?

The input schema has 0% documentation coverage, so the description must compensate. The description lists all valid property values and indicates value types (float or list for colors), adding significant meaning beyond the schema. However, it could specify exact types for each property and value ranges.

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?

Description clearly states the tool sets a property on a material's Principled BSDF node, listing all supported properties. This distinguishes it from siblings like set_material_color and set_material_blend_mode.

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 description lists the properties that can be set, implying usage for those specific fields, but does not explicitly state when to use this tool versus alternatives like set_material_color. No when-not or prerequisites are mentioned.

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