view_set_direction

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

Annotations only say readOnlyHint=false; the description adds the crucial nuance that the call rotates the viewpoint and may alter persisted view state while leaving drawing geometry unmodified. This resolves the ambiguity of what 'not read-only' means here. It stops short of stating whether the persisted view change is undoable or tied to the document save.

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?

Three tight sentences with the core action front-loaded, followed by labeled Side-effects and Disambiguation lines. Every sentence carries information an agent would otherwise have to guess.

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?

With an output schema present, the description needn't describe return values, and it covers the safety profile, the visible effect, and the sibling alternative. The only gap is how the view-state change interacts with undo or save, which an agent might need before mutating state.

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%, so the baseline is 3, but the description adds semantics the schema lacks: the vector is in WCS and is normalized by the tool. It still does not explain how dx/dy/dz relate to the zoom-to-extents step or edge cases such as a zero vector.

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 and resource: set a normalized 3D model-space view direction from a WCS vector, plus the zoom-to-extents behavior. It explicitly distinguishes itself from view_set_preset in the Disambiguation line, so an agent can pick between them without opening either schema.

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 Disambiguation line gives an explicit routing rule: use view_set_preset for standard orthogonal/isometric views, this tool for an arbitrary 3D angle. It does not address when to use the built-in zoom-to-extents versus calling view_zoom_extents, but the core alternative is named.

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