pbr_bake_texture

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

The description states that output is saved to a filepath, which is a minimal behavioral disclosure. But with no annotations providing read-only or destructive hints, the description leaves important behavior undisclosed: it does not say whether the file is overwritten, whether the scene or materials are modified, whether Cycles must be the active engine, or what the tool returns.

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 two short sentences with no filler. The map-type list is dense but useful, and the filepath behavior is stated directly. Every element adds value.

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?

This is a file-writing operation with five parameters, no safety annotations, and no output schema. The description gives the operation and file output, but omits practical context such as prerequisites, side effects, overwrite behavior, and expected result. An agent is left guessing about important runtime behavior.

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 the five parameters. It provides valuable semantics for bake_type by listing valid values, and it references filepath. However, it does not clarify object_name requirements, size units, or samples meaning beyond what the parameter names 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 uses the specific verb 'Bake' and names the resource ('Cycles' maps), then enumerates the exact map types: AO, DIFFUSE, NORMAL, COMBINED, ROUGHNESS, EMIT. It is clearly distinct from all sibling tools, none of which perform texture baking.

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 intended use is implied by the word 'Bake' and the listed map types, so an agent can infer when to call this tool. However, there is no explicit guidance about when not to use it or which alternative to prefer, such as pbr_create_material or pbr_pack_orm.

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