set_viewport_direction

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

No annotations are provided, so the description carries the full burden. It states 'Set viewport direction' but does not disclose any side effects, whether it affects the camera, or if the change is persistent. It is not misleading but adds little beyond the tool's name.

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, front-loaded sentence with no redundant words. It efficiently conveys the action and the parameter values.

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 one-parameter setter with no output schema, the description covers the essentials: what it does and what values are accepted. It lacks only minor behavioral context (e.g., whether the direction change is applied to the current viewport only), but the tool is simple enough that the given info is largely sufficient.

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 input schema only defines a string parameter with no description, and schema coverage is 0%. The description compensates fully by listing all accepted values (front, back, left, right, top, bottom, persp), providing essential information for correct invocation.

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 tool sets the viewport direction and lists the exact supported directions (front, back, left, right, top, bottom, persp), distinguishing it from sibling tools like set_viewport_camera and set_viewport_display.

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 for changing viewport view direction, but does not explicitly mention when to use this tool versus alternatives or any exclusions. The list of directions gives some context, but there is no explicit guidance.

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