camera_look_at

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the action 'point a camera' without explaining side effects such as whether the camera orientation is permanently changed, whether animation keyframes are created, or whether it affects the active camera. No permissions or reversibility info is given.

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 a single concise sentence that directly conveys the core purpose without unnecessary filler. It earns every word.

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 tool has 3 parameters and no annotations, the description is too sparse to be complete. It does not explain how to specify a target vs location, whether both can be omitted, or what happens if both are provided. The presence of an output schema helps but does not compensate for the missing behavioral and parameter 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% (no parameter descriptions). The description mentions 'target object or world location' which hints at the 'target' and 'location' parameters, but it does not explain their format (e.g., target is a string object name, location is an array of numbers) nor does it explain the 'camera' parameter. The description adds minimal interpretive value beyond the 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?

The description uses a specific verb 'point' with a clear resource 'camera' and indicates two target modes: object or world location. This clearly distinguishes it from sibling tools like set_viewport_camera (which sets active camera) and setup_camera_dof (depth of field).

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 implies the tool is for aiming a camera at a target, but it gives no explicit guidance on when to use this vs alternatives, nor does it mention exclusions or prerequisites. It is clear enough for basic use but lacks explicit direction.

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