bake_diffuse_to_atlas

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

No annotations are provided, so the description carries the full burden. It mentions combining materials and repacking UVs, but does not disclose whether the operation is destructive, if it modifies original materials, or what output is generated (e.g., saved file, added nodes).

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 concise, with a clear main sentence and parameter explanations in a structured Args list. No redundant 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?

Despite having 3 parameters and no output schema, the description does not specify the output format, how the atlas is saved, or potential side effects. It also does not differentiate from similar sibling tools like vrc_bake_atlas in this context.

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?

The Args section adds meaning beyond the schema: mesh_names is described as a JSON array, atlas_size as resolution, output_path as custom path. With 0% schema description coverage, this provides necessary context, though descriptions are brief.

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 clearly states the specific action: baking multiple meshes' diffuse colors to a single texture atlas, and mentions combining materials and repacking UVs. This distinguishes it from other baking tools like bake_ao or bake_normal_map.

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 explicit guidance on when to use this tool versus alternatives such as bake_textures or vrc_bake_atlas. The description implies it's for combining diffuse colors of multiple meshes, but lacks when-not-to-use or alternative references.

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