apply_transforms

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

Annotations already flag destructiveHint=true and readOnlyHint=false, so the mutation risk is declared. The description adds real behavioral detail beyond that: shared meshes are made single-user first, children retain their world position, and mirrored negative scale is handled without flipped normals. It stops short of saying whether the bake is undoable or what it 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?

Three tightly packed sentences with the core purpose front-loaded and the Ctrl+A reference immediately orienting the reader. Slightly dense, but every clause carries distinct information about edge-case handling.

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?

With no output schema and annotations covering the safety profile, the description supplies the edge-case behaviors (single-user meshes, child placement, mirrored scale) an agent needs. It omits mode enumeration details and any mode/selection prerequisites, but is broadly sufficient for correct invocation.

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 carry the parameter burden, yet it only expands on `mode: all` (origin goes to world origin) and never explains `scale` or `scale_rotation`, nor the `names` array. Partial compensation gives a baseline 3.

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?

States a specific verb+resource ('Bake the transform of meshes into their vertices') and anchors it to a familiar operator ('as Ctrl+A does'). It does not distinguish itself from nearby siblings such as transform_objects or set_origin, which apply or move transforms rather than baking them.

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 tool versus transform_objects, set_origin, or transform_region, and no preconditions (object mode, selection requirements, undo behavior). The Ctrl+A analogy implies familiar Blender usage but no actual routing guidance is given.

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