ap_set_display_channel

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

With no annotations provided, the description carries the full disclosure burden. It explicitly says the tool changes the 3D viewport display and clarifies that 'lit' is the normal shaded view while other modes isolate a channel or debug output. This meaningfully describes the tool's behavior, though it does not mention side effects or persistence, which are less critical for a viewport display switch.

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 two sentences with no fluff. It front-loads the action and target, exhaustively lists accepted values, and then provides the key clarification about 'lit' versus the other modes. Every word earns its place.

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 single-parameter setter with an exhaustive enum and no output schema, this description is complete. It tells the agent what the tool changes, what values are accepted, and what those values mean in context, so the agent can call it correctly without additional 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 schema already documents every enum value with 100% coverage, so the baseline is 3. The description adds value by explaining that 'lit' is the normal shaded view and all other modes isolate a channel or debug output, giving the agent semantic understanding beyond the raw enum list.

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 uses a specific verb ('Set') and identifies the exact resource ('what the 3D viewport displays') before enumerating all valid modes. This clearly distinguishes it from sibling tools like ap_capture_viewport or ap_set_config, which have different purposes.

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?

The description implies when to use the tool—whenever you need to change the viewport display channel—and explains the semantics of 'lit' versus other modes. However, it does not explicitly state when not to use it or name alternative tools for similar tasks, so the guidance is inferred rather than stated.

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