set_viewport_shading

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the mode values but does not disclose that this is a viewport-only display change, that it does not affect the actual scene data or render output, or whether it requires a particular viewport state. The behavior is implied but not explicitly clarified.

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 compact and front-loads the core purpose in the first sentence. The Args block is minimal and directly relevant. It earns its place with no filler, though the mode list could be integrated more naturally.

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 tool, the description is nearly sufficient, but it lacks any note about viewport-only scope, interaction with render settings, or when a user would want RENDERED versus MATERIAL. Given no annotations and no output schema, a bit more context would make it 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?

Schema description coverage is 0%, so the description must compensate. It does list the four valid mode values, which adds meaning beyond the bare schema property. However, it does not explain the effect of each mode (e.g., MATERIAL shows materials, RENDERED shows render preview), nor does it clarify that the default is SOLID beyond what the schema already states.

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's function: setting the viewport shading mode, and enumerates the four accepted modes (WIREFRAME, SOLID, MATERIAL, RENDERED). It is distinct from sibling tools like set_viewport_camera or toggle_overlays, though it does not explicitly name 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 guidance is given on when to use this tool versus alternatives. The description does not mention that this affects only the viewport display and not the final render, nor does it distinguish it from related viewport tools like toggle_overlays or get_viewport_screenshot.

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