shader_visualize_overdraw

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

With no annotations provided, the description discloses the main behaviors: it captures overdraw visualization, writes an optional .png, and can restore the previous viewport mode. However, it does not explicitly warn that leaving restore_viewmode at its default false may leave the viewport in the overdraw mode after capture, which is a meaningful side effect.

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 front-loaded with the action, then cleanly organizes parameter meanings, a KB reference, and a working example. Every sentence contributes without redundancy or clutter.

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 tool that changes viewport state and writes a file, the description covers the arguments and defaults well and an output schema exists, so return shapes need not be described. The main gap is the missing usage context: when to choose this over sibling rendering/capture tools and the persistent viewport side effect when restore_viewmode is false.

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%, so the parameter annotations carry the full burden. The description compensates well by explaining viewmode's two allowed values, filepath's optional .png output and default directory, and restore_viewmode's behavior.

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 captures an overdraw-focused viewport visualization for material review, naming the specific resource (overdraw viewmode) and the verb (capture. It does not explicitly contrast with sibling tools like renderer_capture_viewmode or shader_analyze_complexity, but the overdraw focus gives enough distinction for purpose clarity.

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 gives no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. 'For material review' is a weak implied context, and the KB pointer is reference material rather than usage direction.

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