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 does not state what effect setting the shading type has on the viewport, whether it affects rendering output, whether it is reversible, or what the return value signifies. The description adds no behavioral context beyond the parameter list.

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 extremely short, but this is under-specification rather than conciseness. It is not a well-structured sentence; it is just a parameter hint. There is no front-loading of purpose or action. The brevity does not serve the agent's needs.

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 one parameter, the description still fails to state the basic action the tool performs. With no output schema details available to the agent (though it exists, it is not provided), the description is wholly inadequate to invoke the tool correctly. An agent would have to infer intent from the name alone.

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 has no enum or description for the 'shading_type' parameter, and schema description coverage is 0%. The description compensates partially by explicitly listing the allowed values (WIREFRAME, SOLID, MATERIAL, RENDERED), which tells the agent what inputs are valid. However, it does not explain what each value represents or any other semantic details, so it is only marginally helpful.

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 is essentially a parameter definition listing 'shading_type: WIREFRAME, SOLID, MATERIAL, RENDERED' rather than a sentence explaining what the tool does. It restates the action implied by the name without explicitly stating 'Set the viewport shading mode to one of these values.' The verb and resource are only implied by the tool name, not the description.

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?

There is no guidance on when to use this tool versus alternatives like set_render_engine or get_viewport_screenshot. No context, prerequisites, or exclusions are mentioned. The agent has no idea when this tool is appropriate.

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