viewport_set_shading

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

No annotations provided, so the description carries full burden. It states the tool sets viewport shading mode but does not disclose side effects (e.g., viewport redraw, persistence), required permissions, or behavior beyond changing mode. The parameter enums are helpful but incomplete for full transparency.

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 short (4 lines), front-loads the purpose, and uses a clear docstring format. Every line adds value, though the 'Args' structure repeats schema info slightly. No wasted words.

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 tool with 3 parameters and no output schema, the description covers the basic purpose and parameter options. However, it lacks usage context, prerequisites, and error behavior, making it minimally complete for an agent to use correctly.

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?

Input schema has 0% description coverage, so the description must compensate. It lists valid values for mode (WIREFRAME, SOLID, MATERIAL, RENDERED) and adds context for studio_light and color_type. However, it does not explain what each mode does or the format for studio_light, leaving gaps.

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 name 'viewport_set_shading' and description 'Set viewport shading mode' clearly specify the action and resource. It distinguishes from siblings like 'viewport_set_overlays' and 'viewport_set_view' by targeting shading mode specifically.

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 explicit guidance on when to use this tool versus alternatives (e.g., other viewport settings). The description only states what it does, not when or when not to use it, leaving the agent without decision support.

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