set_viewport_display

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

No annotations are provided, so the description must disclose behavioral traits. It says 'Set viewport display options' but gives no detail on side effects, scope (e.g., which viewport is affected), persistence, or whether it toggles or overrides settings. This leaves significant uncertainty about the tool's runtime behavior.

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 a single, front-loaded sentence with no wasted words. It directly states the tool's purpose and enumerates its scope, making it easy to parse.

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?

The description is too minimal for an unannotated tool with no output schema. It does not explain possible values for shading_mode, the effect of the guide parameter, or any usage context. An agent would likely need external knowledge to invoke it correctly.

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 description names both parameters ('shading mode, guides'), adding meaning beyond the bare schema. However, it does not describe allowed values for shading_mode or how guide behaves (boolean toggle vs. explicit setting). With 0% schema coverage, this is only partial compensation.

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 tool sets viewport display options and enumerates the specific aspects (shading mode, guides). This provides a specific verb+resource+scope that distinguishes it from sibling viewport tools like set_viewport_camera or set_viewport_renderer.

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. The description does not mention scenarios, prerequisites, or exclusions. It simply states what the tool does without any contextual usage directives.

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