set_viewport_camera

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

With no annotations, the description carries the behavioral burden, and it does meaningful work by stating that the tool reports the camera the viewport is actually looking through and fails if the change did not take. It does not discuss side effects or persistence, but the failure/verification behavior is genuinely useful disclosure.

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 compact and front-loaded with the core purpose, followed by only necessary parameter details. Every sentence contributes operational information with no filler.

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 two-parameter viewport action with no output schema and no annotations, the description gives path-type behavior, optional pane, and failure behavior. It could more explicitly state what happens when pane_name is omitted, but the information needed to call the tool correctly is otherwise present.

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%, so the Args block is the only semantic source of parameter meaning. camera_path is well explained with node path, USD prim path, and Solaris-viewport context, while pane_name only repeats its schema title and adds little semantic value.

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 states a specific verb ('Set'), a specific resource ('the viewport'), and a precise outcome ('look through a specific camera'). The emphasis on camera_path and Solaris viewports distinguishes it clearly from viewport display, renderer, and direction siblings.

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 intended use is implied: use this when the viewport should view through a specific camera. However, it never names alternatives like set_viewport_direction, set_viewport_display, or set_viewport_renderer, nor gives explicit when-not-to-use guidance.

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