ue_set_camera

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

No annotations are present, so the description carries the full burden. It does not disclose side effects, such as whether the camera movement is temporary or persistent, or if a level must be open. The description only states the basic action without behavioral details.

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, consisting of a one-line purpose and two parameter explanations. No superfluous content; every part is necessary.

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 lack of output schema and annotations, the description is too brief. It does not explain the return value, prerequisites, or whether the camera applies to the current viewport or a specific one. Essential context is missing for a tool with 2 optional parameters.

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 meaning beyond the schema by specifying that location is [x, y, z] in cm and rotation is [pitch, yaw, roll] in degrees. This compensates for 0% schema description coverage, though more detail (e.g., coordinate system, relative vs absolute) could improve clarity.

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 'Sposta la camera della viewport' (Move the viewport camera), which clearly indicates the verb and resource. It distinguishes from sibling tools like ue_get_camera (read-only) and ue_set_actor_transform (for actors), but does not explicitly call out differentiation.

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 (e.g., ue_set_actor_transform for actors). The description does not specify prerequisites or context of use.

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