object.apply_transform

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

No behavioral traits are disclosed. The annotations are all false but provide no safety profile; the description does not compensate by explaining side effects, reversibility, permission needs, or impact on scene state. Since this is a transform-apply operation likely mutating objects, the lack of transparency is a serious gap.

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 short, but this is under-specification rather than conciseness. The single sentence adds no functional information and fails to earn its place. It is essentially a placeholder.

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 9 parameters, a complex Blender operation, and many sibling tools, the description is woefully incomplete. It does not explain what 'apply_transform' does, what object it targets, what transform properties are affected, or what the output schema contains. An agent has no basis to call this tool correctly.

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?

The description adds no meaning to any parameter. While the schema provides descriptions for scale, location, rotation, _requestId, _authorization, and _transactionId, the description itself is silent. With 67% schema coverage, the description should compensate for the undocumented params (name, objectId, _expectedSceneRevision), but it does not.

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 merely restates the tool name and command, providing no verb, resource, or effect. It says 'PartMe Blender Harness command `object.apply_transform`' which is a tautology. An agent cannot tell what this tool does or how it differs from sibling tools like blender_object_transform.

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 guidance on when to use this tool versus alternatives. It does not mention prerequisites, context, or exclusions. The only statement about requirements ('Per-request argument checks and session policy still apply') is generic and applies to all tools, not specific usage conditions.

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