qt_vtk_screenshot

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

No annotations are provided, so the description carries the full behavioral burden. It says the tool captures an image, but does not state side effects, whether the operation is read-only, any permission requirements, or what happens with the optional instance parameter; the output schema is the only source of return-value information.

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 brief, front-loaded, and free of filler. The purpose is stated first, followed by a compact Args section, so every sentence contributes to invocation.

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 low-complexity screenshot tool with an output schema, the core required parameter is minimally explained. However, it omits the optional instance parameter and provides no sibling-routing context despite numerous nearby screenshot and snapshot tools, leaving clear gaps.

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 description must compensate for both parameters. It partially explains the required ref as 'Ref to a widget containing a VTK render window,' but never mentions or explains the optional instance parameter, leaving a significant semantic gap.

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 states a specific verb and resource: 'Capture a VTK render window to an image.' This is clear enough to distinguish the core action from generic UI interaction tools, but it does not explicitly differentiate itself from sibling screenshot tools such as qt_screenshot, qt_scene_snapshot, or qt_snapshot.

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 the many screenshot and snapshot siblings. The only usage signal is implicit in the resource named ('VTK render window'), with no exclusions or alternative-routing instructions.

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