blender_apply_transform

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

Annotations are all false, so the description carries the burden of behavioral disclosure. It clearly states that transforms are baked into mesh data, which implies a mutation of mesh data. It does not mention that the object's transform is reset to identity after baking, nor any prerequisites (e.g., objects must have mesh data). While the core behavior is clear, additional side effects are not disclosed, so a 4 is appropriate.

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 sentences with zero fluff. The primary action is front-loaded, and the usage context is immediately clear. Every word contributes to understanding.

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 tool with 5 parameters, no output schema, and no annotation guidance, the description is quite brief. It covers purpose and usage but omits important details such as whether the operation is reversible, what happens to the object transform after baking, and whether it applies only to mesh objects. An agent might call it incorrectly (e.g., on a non-mesh object) without knowing the constraints.

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 only 20% (only response_format has a description). The tool description does not explain any parameters – it does not clarify what 'objects' refers to, nor the meaning of scale, location, or rotation booleans. While parameter names are self-explanatory to Blender users, the description adds no value beyond the schema, and with low coverage it fails to compensate.

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 and resource: 'Bake transforms into mesh data' – this clearly distinguishes it from siblings like blender_set_transform (which sets object transforms) and blender_apply_modifier (which applies modifiers). It also names concrete use cases, making the purpose unambiguous.

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 explicitly states when to use this tool: 'before exporting' or 'when a modifier must see real geometry rather than an object transform'. This gives clear conditions and implies that other tools might be used otherwise. It effectively routes an agent to the right operation without needing to compare with siblings.

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