viewport_mode

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

With no annotations, the description must disclose side effects or constraints. It only states the action and options, omitting whether it resets zoom, affects camera orientation, or has any irreversible consequences. This is a minimal behavioral disclosure for a tool that mutates viewport state.

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 sentence that front-loads the action and immediately lists the available options. Every word earns its place, and there is no redundant information.

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?

The tool is simple with one enum parameter and no output schema. The description covers the essential behavior and enumerates all allowed values. It omits minor details like side effects, but for this low complexity, it is sufficiently 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?

The schema already provides 100% coverage with an enum and description 'View mode'. The tool's description lists the enum values, but adds no extra semantics about the meaning of each mode or how they affect the view. Since schema coverage is high, a baseline of 3 is appropriate.

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 verb 'switch' and the resource 'standard view', then enumerates the exact view options (top, front, right, left, back, bottom, perspective). This unambiguously distinguishes it from sibling tools like viewport_camera or viewport_render_mode.

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 setting standard viewport orientations but does not explicitly contrast with alternatives such as viewport_camera or viewport_look_at. There is no when-not-to-use guidance, leaving the agent to infer the appropriate context from sibling names.

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