viewport_set_view

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

Annotations already provide readOnlyHint=false and destructiveHint=true. The description adds that the operation targets the active viewport, which is useful scope context, but it does not clarify whether the destructive hint refers to view state loss or whether scene geometry is untouched.

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, front-loaded with the action, and lists all allowed values in both Chinese and English with no filler. It is appropriately sized for a one-parameter tool.

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 viewport-switching command, the description plus full enum coverage is nearly sufficient. It could be slightly more complete by addressing the destructiveHint annotation, e.g., clarifying that only the viewport view changes and no scene objects are modified.

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 coverage is 100%: the view parameter has a full enum and a description. The tool description merely repeats the enum values without adding new semantic details about parameter usage or formatting, so the schema carries the burden.

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 a specific verb ('Switch') and resource ('active viewport'), and enumerates the exact accepted standard views. This clearly distinguishes it from sibling viewport tools like viewport_set_shading, viewport_set_layout, and viewport_zoom_extents.

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: call it when you want the active viewport to display a standard view such as top or perspective. However, it does not explicitly state when to prefer an alternative sibling tool or mention exclusions, leaving the routing logic to inference.

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