Open capture viewer

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

The description claims the viewer is 'read-only' but the annotation readOnlyHint is false, indicating possible side effects. This is a contradiction. The description does not disclose behavioral traits beyond annotations, and actually conflicts with them.

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 (one sentence) but lacks necessary details about parameter and behavioral context. It is not overly verbose, but the conciseness comes at the cost of completeness.

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 simple tool with one parameter and no output schema, the description partially covers the return value but omits parameter details and behavioral context. The annotation contradiction further reduces completeness.

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 does not add any meaning to the captureId parameter beyond the schema. With 0% schema description coverage, the description fails to clarify the format or source of captureId.

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 action ('Return a local file URL') and the resource ('read-only Capture Viewer pointing at a stored capture'). It distinguishes from sibling tools like webgl_delete_capture and webgl_export_capture.

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 when needing to open a viewer for a capture, but does not provide explicit guidance on when to use or not use this tool compared to alternatives like webgl_get_capture_overview.

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