Screenshot canvas now

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

Annotations are all false, so the description must convey behavior. It states the screenshot is immediate and saves to a folder, implying a file is created (not read-only). However, it does not disclose potential side effects like overwriting files or permission requirements, leaving gaps.

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 three sentences, front-loading purpose and context. It is concise with no fluff, but the lack of parameter details reduces its efficiency for practical use.

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 5 optional parameters and no output schema, the description is insufficient. It explains the tool's purpose but provides no guidance on how to use parameters, leaving the agent to guess or rely solely on parameter names.

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%, and the tool description provides no information about any of the 5 parameters (label, quality, canvasId, mimeType, canvasIndex). This omission severely hampers correct invocation.

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 takes an immediate canvas screenshot using canvas.toDataURL, distinguishes it from Spector frame captures, and specifies it saves to a screenshots folder. Use cases for visual checks and goal verification are explicit.

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 indicates the tool is for 'any-stage visual checks and goal verification,' implying its general applicability. It contrasts with 'not a Spector frame,' hinting at alternatives like webgl_capture_frame, but does not explicitly state when to avoid this tool.

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