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, but it only states that the transform is set. It does not disclose whether this modifies persisted editor state, whether null parameters mean 'keep current value', or what coordinate conventions are used.

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, tightly worded sentence with no filler. It is appropriately front-loaded and easy to scan, though its brevity contributes to missing behavioral and parameter details.

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 lack of annotations and 0% parameter description coverage, this definition is too thin for an agent to invoke correctly. An agent cannot determine whether position and rotation are expected simultaneously, what units to use, or how null values behave. The existence of an output schema does not make up for the missing input semantics.

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?

The schema has two parameters with 0% description coverage, and the description does not compensate. It never mentions position or rotation explicitly, and it does not explain array length, units, rotation ordering, or what null means for each parameter.

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 names a specific verb ('Set') and a specific resource ('active editor viewport camera transform'). This distinguishes it from sibling tools like get_viewport_camera, which reads the camera, and set_transform, which likely targets an entity rather than the editor 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?

The description provides no explicit guidance on when to use this tool versus alternatives such as get_viewport_camera, set_transform, or capture_viewport. The only context is implied by the tool's name and phrasing, with no exclusions or prerequisites stated.

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