ue_set_camera

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

The description indicates that this is a mutation (moving camera) and specifies rotation order and units. However, no annotations exist, so it carries full burden. It does not disclose whether the camera movement is instantaneous, animated, or requires a viewport. No error conditions or side effects mentioned.

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?

Extremely concise: two sentences, no fluff. First sentence states the action, second clarifies rotation format. Efficient and front-loaded.

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?

No output schema, so description should explain what the user gets back (e.g., success flag). It does not. It also lacks prerequisites (e.g., viewport must be active). For a simple camera move, it is adequate but not thorough. Sibling tools like ue_get_camera or ue_set_actor_transform might require more context.

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?

Schema description coverage is 0%, so description must compensate. It adds meaning for 'rotation' (roll, pitch, yaw in degrees) but says nothing about 'location' (units, coordinate system, or format). Only partially compensates for the undocumented parameters.

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 'Move the editor viewport camera' which is a specific verb-resource pair. It distinguishes from siblings like ue_get_camera (get state) and ue_set_actor_transform (set actor transform). It also specifies rotation format.

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 on when to use this tool versus alternatives. Does not mention any prerequisites, exclusions, or context for use. For example, when to use this over ue_focus_actor or ue_set_actor_transform is not indicated.

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