set_baking_mesh_inputs

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

With no annotations, the description carries the full burden. It does not disclose what 'sandboxed' means operationally, what happens to previously assigned meshes, why a 'confirm' flag exists, or whether the operation is reversible. For a mutation tool with zero annotation coverage this is a substantial gap.

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?

A single efficient sentence with the primary resource front-loaded. It is not padded, though the terseness is part of the under-specification problem.

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?

An output schema exists, so return values need not be explained, but six parameters at 0% coverage plus no annotations and no usage routing leaves the definition too thin for correct invocation of a mutation 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?

Schema description coverage is 0%, so the schema documents only names and types for all six parameters. The description gestures at high_poly_files and cage inputs but says nothing about cage_mode values, low_as_high, texture_set, or the confirm flag, leaving most semantics unexplained.

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 states a specific verb ('Assign') and resource ('high-poly/cage meshes') plus a secondary scope ('common baker settings'), which clearly separates it from bake-execution siblings like start_bake. It does not explicitly distinguish itself from configure_baking or set_baking_resource_input, so it stops short of a 5.

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?

There is no statement of when to use this versus configure_baking, inspect_baking_parameters, or set_baking_resource_input, and no preconditions such as needing an existing bake configuration. The agent must infer placement in the workflow from the name alone.

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