material.create_pbr

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

Annotations provide readOnlyHint=false, openWorldHint=false, idempotentHint=false, destructiveHint=false, but the description adds no behavioral context beyond generic 'per-request argument checks and session policy'. It does not disclose side effects, scene mutations, or output behavior, and it contradicts nothing.

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 text is short but this is under-specification rather than conciseness. It includes boilerplate about risk and maturity that adds no actionable value and omits the core function. The structure is not front-loaded with useful information.

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's complexity (9 parameters, nested array for baseColor, multiple internal fields) and an output schema, the description is entirely inadequate. It does not explain what the tool returns, how it affects the scene, or how parameters map to Blender's PBR material properties, making safe and correct invocation impossible.

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 only 33%, and the description provides no explanation of the material parameters (name, alpha, metallic, baseColor, roughness). It does not compensate for the undocumented fields, so an agent cannot infer valid ranges or units beyond what the schema's basic types imply.

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 only repeats the command name and gives generic metadata (risk, maturity) without stating what the tool actually does. It fails to specify that it creates a PBR material or what 'PBR' entails, leaving the agent to guess from the name alone.

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?

No guidance is provided on when to use this tool versus the many other material-related siblings (e.g., material_create_node_group, material_assign). There is no mention of prerequisites, target objects, or typical workflows, so an agent cannot decide when to invoke it.

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