viewport_mode_set

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

Annotations already declare destructiveHint=true and openWorldHint=false, so the safety profile is covered structurally. The description contributes the constraint that the input must be an exact native enum name, but says nothing about what state is altered, whether a prior mode is recoverable, or how invalid names are rejected.

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?

One short sentence with no filler, front-loading the verb and target. It is efficient but slightly under-specified rather than overly verbose.

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 mutation tool with a destructive hint, no output schema, and a free-form string parameter, an agent still lacks the two things it needs: where to obtain valid enum names and what the call changes. The annotations cover risk but not the procedural gap.

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 single 'mode' parameter is a bare string with no enum, so the description carries the full burden. It only obliquely signals that valid values are a discovered native enum set and gives no format examples or pointer to where those names are listed.

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 pairs a specific verb ('Set') with a specific resource ('native ViewportMode enum'), so the agent knows this changes the viewport's render mode. It does not differentiate itself from the neighboring viewport tool (viewport_capture), but the core action is unambiguous.

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?

'Exact discovered native ViewportMode enum name' implies the value cannot be invented and must come from prior discovery, which is useful implicit guidance. However, it never names the discovery tool (api_inspect / native_tool_inspect / native_tools_list) nor states when to prefer this over other viewport settings.

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