blender_materials_baking

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

Annotations are all false, leaving the description to carry the burden. The description only states the conversion outcome but doesn't disclose side effects such as file writes, material modifications, or whether original materials are backed up. The mention of 'Prevents Semantic Dilution' is a value proposition, not a behavioral disclosure.

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: the first gives the core function, the second gives the use case. No redundant words, and the marketing-like 'Semantic Dilution' phrase adds a memorable rationale.

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 (10 params, multiple operations), the description is somewhat thin. It focuses on one operation (convert shaders) but doesn't mention other operations like consolidate_materials or optimize_for_mobile. Output schema covers return values, but the description doesn't address when to use different operations or what side effects occur, leaving gaps.

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?

All 10 parameters have schema descriptions (100% coverage), so the baseline is 3. The description doesn't elaborate on parameter meanings beyond the schema, but the high-level purpose helps interpret parameters like 'operation' and 'bake_type' in the context of converting VRM/MToon to PBR.

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 opens with 'Convert non-standard (VRM/MToon) shaders to PBR textures,' which clearly states the tool's action and target. It distinguishes from sibling tools like blender_shaders or blender_materials by focusing on conversion to PBR, and the Resonite/Unity context adds specificity.

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 phrase 'Essential for VRM avatars moving into Resonite, Unity, or other PBR-based environments' provides a clear when-to-use context. However, it doesn't name alternatives or specify when not to use, so it's not a 5.

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