ue_focus_actor

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

With no annotations, description carries full burden. It explains the tool moves the camera to focus on an actor at a specified distance, with defaults for both parameters. Potential side effects (like whether it modifies the actor) are not discussed, but the behavior is simple and non-destructive by nature.

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?

Description is short (three sentences plus parameter list), front-loaded with purpose, and every sentence adds value. No wasted words.

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?

For a simple focus tool with no annotations or output schema, description covers purpose, usage context, and parameters. It could mention return value (likely none), but overall adequate.

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 description must add value. It explains both parameters: 'label' is the actor to focus (defaults to current selection) and 'distance' is camera distance in cm (default 500). This adds meaning beyond the plain schema.

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?

Description clearly states the tool focuses the camera on an actor, comparing it to the F key in the editor. It also distinguishes itself from sibling ue_screenshot by explaining how they complement each other.

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?

Provides clear context by linking to ue_screenshot, implying use before taking screenshots. However, it does not explicitly mention when not to use or list alternatives beyond that sibling.

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