set_viewport_direction

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

No annotations are supplied, so the description carries the full burden. It does add a genuinely useful behavioral constraint by enumerating the legal direction values, which the schema does not, but it says nothing about which viewport is affected, whether the change is persistent/undoable, or any auth/state requirements.

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?

A single front-loaded sentence with the action first and the value list second; no filler or redundancy.

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?

An output schema exists so return values need not be explained, and the sole parameter is fully enumerated. The only real gap is scope – it does not say whether the direction applies to the active pane or all viewports.

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 0% and the schema exposes 'direction' as a bare string with no enum. The description compensates by listing all seven valid values (front, back, left, right, top, bottom, persp), which is exactly the semantics an agent needs to avoid an invalid call.

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?

States a specific verb (Set) and resource (viewport direction) and enumerates the accepted directions. It is distinguishable from siblings like set_viewport_camera or set_viewport_display, though it never explicitly contrasts itself with them.

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 when-to-use or when-not-to-use guidance. An agent is left to infer that this snaps the view to an axis while set_viewport_camera presumably sets an arbitrary camera, and nothing is said about preconditions (e.g., whether a viewport must be active).

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