blender_bake_pbr

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

Discloses the use of Blender CYCLES Bake and outputs generated, but lacks details on prerequisites (e.g., Blender installation), side effects (e.g., overwriting files), performance implications, or error conditions. Annotations provide no additional behavioral hints, so description carries burden but only partially addresses it.

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?

Two concise sentences, front-loaded with primary action and outputs, followed by usage example. No redundant or wasted words. Uses bold for emphasis and examples for clarity.

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?

Covers inputs (preset, resolution, output directory) and outputs (texture maps) adequately given no output schema. Explains integration with Unity via build_scene. Missing return value or error handling info, but overall sufficient for a baking tool.

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?

With 0% schema coverage, description compensates by listing preset values (brick, rock, wood, metal) and resolution examples (512, 1024, 2048). However, out_dir is only implied via Unity integration mention; no format or naming convention specified. Adds some meaning but not comprehensive.

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 it creates a tileable PBR texture set via Blender CYCLES Bake, specifying output maps (baseColor, normal, roughness, ao). It distinguishes from sibling download tools by emphasizing 'eigene Premium-Texturen ohne Download' (own premium textures without download).

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?

Explicitly suggests usage for textures not available in CC0 libraries ('für Dinge, die keine CC0-Bibliothek hat'). Provides context for when this tool is appropriate, though does not explicitly exclude other scenarios or compare with alternatives like search_pbr_materials.

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