blender_object_apply_transforms

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It does communicate that transforms are baked into mesh data, implying permanent modification, but it does not explicitly warn about irreversibility, potential side effects on children/constraints, or whether only mesh objects are supported. This is adequate but not fully transparent.

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 a single, focused sentence with no filler. It front-loads the operation, specifies the target resource, and describes the result, so every word earns its place.

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?

For a mutating tool with no annotations and no output schema, the description captures the core effect and scope clearly. The schema covers parameter semantics, and the description explains the operation's purpose and result. Minor gaps remain around irreversibility and explicit exclusions, but the tool can be invoked correctly based on the provided information.

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 input schema already documents all four parameters at 100% coverage, giving a baseline of 3. The description adds value by explaining that the location/rotation/scale booleans correspond to those transforms being reset to identity after baking, which clarifies their effect beyond the schema's simple 'Apply ...' labels.

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 a specific verb ('Apply (bake)') and names the resource ('object transforms') with a clear outcome ('location/rotation/scale reset to identity'). This distinguishes it from related tools like blender_object_transform, which changes transforms rather than baking them into mesh data.

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 description implies when to use the tool—when transforms should be baked into mesh data so they reset to identity—but it does not explicitly state when not to use it or name alternatives such as blender_object_transform or blender_object_set_origin. The usage context is inferred rather than explicit.

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