lookdev_camera

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 implies scene mutation (placing a camera) but says nothing about side effects, permissions, whether an existing camera is replaced, or how the bbox/aiming is computed.

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?

Two short sentences, front-loaded with the core action, so it is not bloated. The second sentence, however, is unclear enough that it reads as noise rather than earning its place.

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?

An output schema exists, so return values need not be explained, but for a 6-parameter mutation tool with zero annotation and zero schema-description coverage, the two-line description leaves the agent without enough to invoke it 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 description coverage is 0% across 6 parameters (name, look_at, lop_path, input_path, parent_path, distance_scale), yet the description names none of them. 'looking at a prim bbox' loosely hints at look_at and the USD prim reference at input_path, but defaults, formats, and path semantics are entirely undocumented.

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 first sentence gives a recognizable verb+resource ('Place a LOP Camera looking at a prim bbox'), so an agent can tell it creates a camera aimed at a prim. However, the second sentence ('Look through the USD prim string') is garbled and does not clarify the action or differentiate it from siblings like lookdev_dome or set_viewport_camera.

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?

There is no statement of when to use this tool versus alternatives such as frame_usd_prim, set_viewport_camera, or the other lookdev_* tools. The agent must infer context from the name alone.

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