shading-prepare_pbr_maps

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

No annotations are present, so the description carries full burden. It only mentions 'create image slots' without disclosing side effects (e.g., node tree modifications, possible overwriting, material creation/reuse, object requirements). This is a significant gap for a tool that likely mutates the scene's node graph.

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, clear sentence with no wasted words. It front-loads the action and scope, making it easy to parse quickly.

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 (5 parameters, likely creates a node group), the one-line description is insufficient. It lacks information about prerequisites, return values (no output schema), potential side effects, or error conditions. The description does not stand alone to guide an agent effectively.

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 0%, so the description must compensate for parameter understanding. It does not mention any of the five parameters (maps, size, object, prefix, material), while the schema only provides brief titles. The description adds no value beyond the schema's minimal metadata.

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 explicitly states the action ('Create') and the resource ('node-based PBR image slots'), listing the exact map types (BASE_COLOR, NORMAL, ROUGHNESS, AO, CAVITY). This clearly distinguishes it from siblings like shading-add_image_texture or shading-create_material by focusing on a multi-slot PBR setup.

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 implies usage for setting up PBR maps but gives no explicit guidance on when to use this tool versus alternatives like shading-add_image_texture or shading-set_principled. No exclusions or alternative recommendations are provided, so usage context is only implied.

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