set_karma_quality

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

With no annotations, the description carries the full burden, and it does disclose real behavior: the viewport sample API is reported unavailable rather than faked, and pause is delegated to setRendererPaused with a 'pause_honored' result. That is genuine non-obvious behavior, but nothing is said about whether the call mutates scene state, requires a LOP context, or has side effects.

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?

It is short and front-loads the topic, but the three fragments are telegraphic and under-specified rather than tight; the single-sentence openers trade clarity for brevity.

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?

An output schema exists so return values need not be restated, yet 6 parameters at 0% coverage go undocumented and the tool's core action is never articulated. For a 6-param tool with no annotations, this leaves major gaps an agent must fill by trial.

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% for 6 parameters, and the description documents only the semantics of 'paused'. 'viewer', 'preview', 'samples', 'lop_path', and 'parent_path' are entirely unexplained in both the schema and the description, leaving the agent to guess.

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 opener 'Karma viewport quality' is a topic label, not a verb+resource statement of what the tool does. It never states that it sets/applies quality settings, and the 'H22 has no pixel-sample HOM; LOP settings are the knob' line is internal jargon an agent cannot decode into an action.

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 a partial routing hint ('paused goes through setRendererPaused'), which implicitly tells the agent not to expect pause handling here, but there is no stated when-to-use versus siblings like set_viewport_display, set_hydra_display, or set_renderer_paused.

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