set_viewport_display

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

With no annotations provided, the description carries the burden of behavioral disclosure. It explicitly mentions NO_UNDO (not entering the undo group), 'only UI/view write', whitelist token constraints, and response cap handling. This is substantial transparency, though it omits error handling or exact return details.

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, front-loaded with the purpose, and packs essential behavioral constraints into a few sentences without redundant information. Each sentence contributes value.

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 setter with three string parameters and no output schema, the description covers purpose, key constraints, and side effects. It lacks usage context and error behavior, but the simplicity of the tool and the disclosed constraints make it reasonably complete.

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 provides only parameter names with 0% coverage. The description adds that display_set and shaded_mode must be whitelist tokens and that reflective setters/non-existent enums are rejected, but it doesn't explain the meaning of each parameter or provide allowed values. ctx remains entirely unexplained. It partially compensates but leaves significant 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 description clearly states it sets the viewport display set and shaded mode, using a specific verb and resource. This distinguishes it from sibling tools like set_viewport_camera and set_viewport_direction, which target different aspects of viewport control.

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 does not explicitly say when to use this tool versus alternatives like set_viewport_camera or set_viewport_renderer. It implies usage for viewport display via the purpose, but lacks exclusions, prerequisites, or alternative comparisons.

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