set_viewport_camera

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states that it sets the camera location and/or rotation, which is the core behavior, but it does not mention coordinate conventions, units, defaults when both fields are omitted, or any side effects on the editor state. For a simple setter, this is adequate but minimal.

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, clear sentence that front-loads the action and target. It contains no filler or redundant information, and every word contributes meaning.

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?

The tool is simple, with a moderately detailed schema and no output schema. The description explains the essential purpose but leaves gaps such as coordinate system, rotation order, and behavior when no parameters are provided. It is minimally complete but not fully self-contained.

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 100% ('Camera location' and 'Camera rotation'), so the schema already documents the parameters. The description adds no additional semantics beyond what the schema provides, such as units or coordinate system, so a baseline score of 3 is appropriate.

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 the specific verb 'Set' and identifies the resource as 'editor viewport camera location and/or rotation', clearly distinguishing from the sibling 'get_viewport_camera' which reads the camera state. It precisely communicates the action and scope.

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 usage (when you need to adjust the camera position or orientation) but provides no explicit guidance about when to use this tool versus alternatives, nor any exclusions or prerequisites. It relies on the name and verb to imply context.

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