ue_set_actor_transform

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

With no annotations, the description carries the full burden of disclosing behavioral traits. It indicates mutation ('modifica') but fails to mention potential side effects, required permissions, whether the transform change is absolute or relative, or if it triggers any events. For a mutation tool, this is insufficient.

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?

A single sentence that directly conveys the tool's purpose without any filler. The front-loading is effective—the core action and target are clear immediately.

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 is too sparse for a tool with 4 parameters and no output schema. It does not explain the effect on other transform properties when some are omitted, error handling (e.g., if label not found), or any behavioral context like whether it works in play mode. Significant gaps remain.

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 maps Italian terms to parameters ('posizione/rotazione/scala' to location/rotation/scale) and clarifies that 'label' identifies the actor. However, it does not explain the expected format of the arrays (e.g., [x,y,z] units) or default behavior. With 0% schema coverage, this adds minimal value beyond the parameter names.

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 it modifies the transform (position/rotation/scale) of an actor identified by its label. The verb+resource combination is specific, but it does not distinguish from sibling tools that also modify actors, such as ue_set_replication or ue_set_class_defaults.

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, context (e.g., must be in edit mode), or when not to use it. This leaves the agent without decision-making support.

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