set_viewport_camera

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

The idempotentHint annotation already indicates the operation is safe to repeat, and the description adds the useful detail that passing None restores the default camera. It does not disclose error behavior for invalid camera names or what the output contains, but the output schema likely covers return values.

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 with no filler. The primary purpose is front-loaded, and the parameter instruction is clear and complete.

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 single-parameter, idempotent setter with an output schema, the description covers the essential behavioral contract. It could be more complete by addressing the overlap with set_active_camera, but nothing critical is missing for basic invocation.

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 description must carry the parameter meaning. It does so effectively by explaining that the 'camera' parameter is a camera object name and that None means the default camera, which is more informative than the raw schema.

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 action ('Set the active camera') and the target resource ('the viewport'), and it specifies how to invoke it with a camera object name or None. However, it does not distinguish itself from the sibling tool set_active_camera, which appears to serve a very similar purpose.

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 guidance about when to use this tool versus set_active_camera or other camera-related tools like camera_look_at. The only usage hint is the parameter instruction, which is not enough to route an agent to the correct alternative in ambiguous situations.

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