ac_camera_look_at

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

No annotations exist, so the description carries the full burden. 'Hold the camera' hints that the setting persists, but the description doesn't say whether this switches camera mode away from free/mode, whether it is reversible, what happens on subsequent frames, or that `fov` is left unchanged when omitted.

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?

One dense sentence, front-loaded with the core action and no filler. Its brevity comes at the cost of omitting `fov`, but nothing is redundant.

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?

A three-parameter tool with no annotations, no output schema, and 0% schema coverage needs more from the description than a single sentence. The `fov` parameter and the relationship to the other camera tools (`ac_camera_free`, `ac_camera_mode`) are unaddressed.

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 compensate, and it does partially: it explains that `pos` and `target` are [x, y, z] triples in AC world coordinates. However, the third parameter `fov` is never mentioned in either the description or schema, leaving its meaning (and the `0` default) opaque.

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?

States a specific action: place the camera at `pos` and orient it toward `target`. That distinguishes it from `ac_camera_free` and `ac_camera_mode` by implication, though it never names those siblings or contrasts with them explicitly.

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 when-to-use or when-not-to-use guidance. An agent must infer from the tool name alone whether this is a one-shot reposition, a persistent mode, or how it interacts with `ac_camera_free` / `ac_camera_mode`.

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