ue_focus_actor

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

No annotations are provided, so the description carries the full burden. It explains that the tool moves the camera to focus on an actor, similar to the F key, and that using the selection when no label is given. However, it does not disclose potential side effects like persistence of camera position or any constraints.

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 concise, with two short paragraphs followed by an Args section. It front-loads the purpose and context, and each sentence adds value. Could be slightly more compact, but overall efficient.

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 simplicity of the tool (2 optional parameters, no output schema), the description covers the essential aspects: what it does, how parameters work, and relationship to a sibling tool. It is complete enough for an agent to select and invoke 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?

Schema coverage is 0%, so the description must add meaning for parameters. It does so effectively: label is 'actor to focus; if omitted uses current selection,' and distance is 'camera distance in cm (default 500).' This provides clear guidance beyond the schema's type and default.

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 the tool focuses an actor with the camera, analogous to the F key in the editor. It distinguishes from sibling ue_screenshot by explaining that without it, the screenshot captures whatever the camera was already looking at, which is rarely the newly built object.

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?

The description provides clear context on when to use this tool: as a complement to ue_screenshot to frame the actor before capturing. It implies that without this, the screenshot may not capture the intended actor. However, it does not explicitly state cases where the tool should not be used.

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