apply_transforms

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

With no annotations, the description carries the burden of disclosing side effects and explicitly warns that the mesh is modified and a checkpoint should be created first. It could add more detail about multi-user data refusal or transform reset, but the core destructive behavior is disclosed.

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 short sentences lead with the action, provide the use-case rationale, and end with a necessary warning. There is no filler or redundant restatement.

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 mesh tool with no output schema, the description supplies purpose, domain rationale, and a destructive-operation warning. It relies on the schema for parameter details, which is acceptable because force_multi_user and location behaviors are already documented there.

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 60%, so the description must help with the undocumented scale and rotation booleans; it does clarify that scale ends at exactly 1. However, it doesn't mention the location option or add much beyond what the schema already provides for names and force_multi_user.

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 exactly what the tool does: bakes rotation and scale into mesh data. This clearly distinguishes it from transform-setter siblings like set_transform, rotate_object, and scale_object by focusing on mesh data mutation.

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 provides clear context ('Game engines generally expect...') that tells an agent when this preparation step is appropriate. It also warns the user to checkpoint first, but it does not name alternatives or give explicit when-not-to-use conditions.

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