Freeze Transforms

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

Annotations already note destructiveHint=true and idempotentHint=true; the description adds the key behavioral detail that it 'applies current values as identity', explaining how the transformation is effectively preserved while resetting values.

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?

Single, clear sentence with no redundant words. Front-loaded with action and resource. Could benefit from a brief usage hint, but it's concise and direct.

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?

Though the tool is simple (4 boolean params, 1 required), the description does not confirm it modifies node transform attributes, nor mention output schema content (e.g., returns success). With annotations and high schema coverage, it's minimally 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?

Input schema covers all 4 parameters with individual descriptions (nodes, scale, rotate, translate) at 100% coverage. The tool description adds no additional meaning beyond the phrase 'freeze transforms', so baseline 3 is appropriate.

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 resets transforms to identity, using specific verbs 'freeze' and 'reset', and distinguishes it from siblings like set_pivot which adjust pivot positions.

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?

No explicit guidance on when to use this tool versus alternatives like attributes.set or modeling.center_pivot. The description implies it's for resetting transforms after manipulation, but lacks when-not-to-use or prerequisite information.

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