blender_material_set_principled

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

The description gives no information about side effects, such as whether the material must exist, whether the shader node is created if missing, or what happens if parameters are invalid. With no annotations, the description carries the full burden and fails to disclose any behavioral details.

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 a single concise sentence with no fluff, which is appropriate for the tool's purpose. However, it could be slightly expanded to include usage context without becoming verbose, so it's not perfectly balanced.

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?

Given the tool has 8 parameters and no output schema, the description is too sparse. It lacks details about how the parameters interact, whether the material must be selected or named, and what the expected outcome is. This leaves the agent without enough context to use the tool 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?

The schema covers all parameters with descriptions (100% coverage), but the tool description adds no additional meaning. It does not explain parameter relationships, defaults, or which parameters are required beyond the schema's required field. Since schema coverage is high, a baseline of 3 is appropriate.

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 'Configure' and a specific resource 'Principled BSDF shader parameters', making it clear that this tool adjusts PBR material settings. However, it could be more explicit about the scope compared to other material tools like set_color or add_texture, so it's not fully distinctive.

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 provides no guidance on when to use this tool over alternatives such as blender_material_set_color or blender_material_add_texture. It does not mention prerequisites like an existing material or the presence of a Principled BSDF node.

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