set_viewport_camera

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

No annotations are provided, so the description must carry the full burden. It fails to disclose important behavioral aspects such as whether the operation is reversible, what happens if the specified camera does not exist, or whether the change is permanent or session-only. It also does not indicate if there are any side effects on the scene or rendering.

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 very concise and front-loaded with the primary action. It uses a clear structure with an Args section and a short, direct sentence. No unnecessary information is included, making it easy to parse, but it is too brief to carry all necessary semantics.

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's complexity is low (one parameter), the description is insufficient. There is no output schema to describe return values, and the description does not explain how the camera is selected or how to list available cameras. Given the existence of sibling tools like list_lights and list_materials, one might expect a list_cameras tool, but that is not referenced. The description leaves the agent with ambiguity about camera naming and behavior.

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%, meaning the description is the only source of parameter information. It states the meaning of empty string = auto, but it does not explain what a non-empty string should be (e.g., a camera name or identifier). It lacks details on format, validation, or behavior for invalid names.

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 clearly states the primary purpose: setting the active viewport camera. It identifies the resource (viewport camera) and the main action (set active). However, it does not explicitly differentiate from sibling tools like configure_camera or set_camera_to_view, which might have overlapping functionality.

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 provides minimal guidance on when to use it. It only hints at the camera_name parameter with a default of empty string for auto, but it does not explain when to use an empty string versus a specific camera name, nor does it describe any alternatives. There is no mention of prerequisites or expected context.

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