set_viewport_view

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

With no annotations, the description alone must disclose behavior. It states that the tool sets the camera view, but does not mention side effects, whether it modifies the model, what it returns, or any prerequisites like having a viewport open. This is a minimal behavioral statement with little transparency beyond the tool's obvious purpose.

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 action stated first and the parameter values listed clearly. It earns its length with the useful view_type enumeration, though it omits contextual information that could be added without much bloat.

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 setter tool, the essential calling information (view_type values, default) is present, and there are no required parameters. However, timeout semantics are undocumented, and there is no guidance on how this viewport tool relates to its viewport-focused siblings, leaving the description minimally viable rather than complete.

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 compensate. It does document the view_type values ('iso', 'front', 'back', 'top', 'bottom', 'left', 'right'), which adds real meaning beyond the plain schema. However, the timeout parameter is not explained at all, leaving a gap in parameter understanding.

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 action and resource: it sets the camera view in the viewport, and lists the exact view types. This is clear and distinct from the sibling viewport tools in function, though it does not explicitly call out how it differs from set_viewport_display or related tools.

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?

No guidance is given about when to use this tool versus alternatives such as set_viewport_display, capture_viewport, or get_viewport_image. The intended use is only implied by the action phrase; there are no exclusions, preconditions, or alternative-selection hints.

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