viewport_set_overlays

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

With no annotations, the description must cover behavioral traits. It lists parameters with brief explanations (e.g., 'use of for debugging'). However, it does not disclose whether changes affect all viewports, require a specific mode, or have side effects. Behavior is straightforward but lacks scope context.

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 and well-structured: a one-line intent followed by an argument list. Each parameter on its own line with a short explanation. No superfluous text.

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?

Given simplicity (all booleans, no output schema), the description adequately covers the tool's function and parameters. Missing is the scope of effect (e.g., active viewport only, all viewports) and whether it toggles or sets absolutely, but overall sufficient for a configuration tool.

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 coverage is 0%, so description must compensate. It enumerates all 7 parameters with explanations that add meaning beyond schema titles, such as 'Master overlay toggle' for show_overlays and 'useful for debugging' for show_face_orientation. This provides clear context for each boolean.

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 'Configure viewport overlays' clearly states the verb (Configure) and resource (viewport overlays). It distinguishes from sibling viewport tools like viewport_set_shading or viewport_set_view by focusing on overlays specifically.

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 usage for controlling overlay visibility but does not provide explicit guidance on when to use this tool versus alternatives, nor when not to use it. No mention of prerequisites or context.

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