object-transform_apply

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

No annotations exist, and the description reveals no side effects, permissions, or potential impacts (e.g., object rotation/scale being reset). It does not disclose any behavioral traits beyond the bare action.

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 brief, which makes it concise, but it is too short to be informative given the tool's complexity. It lacks a proper structure to convey necessary details, though it does avoid verbosity.

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?

The description fails to provide sufficient context. It does not explain what applying a transform means, the effect on the object, or the role of the parameters. Without this, the tool is not adequately described for a user to understand its functionality.

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 extra meaning to the schema parameters. The boolean flags (scale, location, rotation, properties, isolate_users) are not explained, leaving their purpose unclear from the description alone.

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 the action ('Apply') and the resource ('an object's transform'), but it is vague and does not distinguish this from sibling tools like object-transform_set or object-origin_set. It lacks specificity on what 'apply' entails.

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 guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, scenarios, or why one would choose this over similar transform operations.

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