set_viewport_renderer

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

With no annotations, the description carries the full burden for behavioral disclosure. It provides no information about side effects, required render nodes, or valid renderer values. The one-line sentence adds no behavioral context beyond the tool's name.

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 concise at one sentence, but it is under-specified. It is not overly verbose, but it lacks the contextual detail expected for a useful tool description, making it more trivial than appropriately concise.

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 tool with no annotations, no output schema, and an unelaborated parameter, the description is severely incomplete. It does not explain renderer options, the effect of setting the viewport renderer, or any related configuration, leaving the agent without essential information.

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 input schema defines a single required string parameter 'renderer' with no description or enums. The description does not compensate, offering no examples, values, or meaning for the parameter. Schema description coverage is 0%, and the description fails to bridge that gap.

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 action (set) and the resource (viewport renderer), distinguishing it from sibling tools like set_viewport_camera and set_viewport_display. It is specific and unambiguous, though it does not elaborate on the renderer concept or variations.

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 usage guidance is provided. The description does not indicate when to use this tool versus related tools such as set_render_settings or list_render_nodes, nor any prerequisites or expected context.

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