Capture next frame

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

Annotations are minimal (all hints false), so the description carries the burden. It discloses that the tool auto-connects, performs readiness checks, and installs the runtime if needed, which are significant behavioral traits. It also states that the return value is a summary with resource URIs, not full JSON, setting accurate expectations.

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 two sentences, front-loaded with the core action, and every clause adds value. No unnecessary words.

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 the tool has 9 parameters, no output schema, and minimal annotations, the description is too brief. It does not explain key parameters like triggerMode or the content of the 'summary,' leaving agents with insufficient context to use the tool 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?

Schema description coverage is only 33%, and the description does not add any meaning to the parameters. It fails to compensate for the low coverage, leaving many parameters (e.g., triggerMode, fullCapture, includeThumbnails) unexplained.

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 starts with 'Capture the next WebGL frame,' which is a specific verb+resource. It clearly distinguishes from sibling tools like webgl_screenshot_canvas or webgl_capture_sequence.

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 mentions auto-connects and installs runtime, implying when this tool is used (for a single frame capture). However, it does not provide explicit guidance on when to use this tool versus alternatives like webgl_screenshot_canvas or webgl_capture_sequence, nor are exclusions or prerequisites stated.

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