apply_transform

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

With no annotations provided, the description carries the full burden. It states the transform reset action but does not disclose potential side effects (e.g., whether it is destructive or reversible), required permissions, or behavior on locked/protected objects. The description is adequate but lacks depth.

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 extremely concise: two sentences with no fluff. The first sentence defines the action, the second provides context. Every word adds value, making it easy to parse quickly.

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?

Given the tool's simplicity (4 params, only 1 required), the description covers the purpose and usage context. However, it falls short by not addressing parameter meanings or behavioral edge cases (e.g., what if the object has constraints?). Completeness is adequate but not thorough.

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 compensate by explaining parameters. It mentions nothing about the 'name' parameter or the boolean flags (scale, location, rotation). The agent is left to infer from parameter names and defaults, which is insufficient for correct invocation.

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 clearly states the tool's action: 'Apply (freeze) the object's transforms, resetting them to identity.' It distinguishes from sibling tools like 'apply_modifier' by specifying it operates on transforms, not modifiers. The context of when it's essential (before export, after non-uniform scaling) further clarifies its unique role.

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 explicit use cases: 'Essential before export or after non-uniform scaling.' This guides the agent on appropriate contexts. However, it does not specify when not to use the tool or mention alternative tools, which would be helpful for differentiation.

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