autoflow_capture_screenshot

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

With no annotations provided, the description carries the full behavioral burden. It clearly states the tool captures a JPEG screenshot and implies a non-mutating, read-only operation by framing the result as visual inspection material. It does not explain how the screenshot is returned or stored, but for a zero-parameter screenshot action this is a minor gap.

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 one concise sentence with no filler. It front-loads the action and output format, then presents the intended use cases. Every clause earns its place.

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, zero-parameter tool with no output schema, the description gives the essential context: what is captured, in what format, and why the agent would want it. It could explicitly state how the screenshot is delivered or that it does not alter the project, but the current level is adequate and close to complete.

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 tool has zero parameters and the schema description coverage is 100%, so there is no parameter information for the description to add. The baseline of 4 applies because no parameter semantics are needed.

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 uses a specific verb ('Capture') and a concrete resource ('visual JPEG screenshot of the Google Flow project workspace'), then states three clear purposes: inspect progress, verify visual output, and diagnose UI state. This fully distinguishes the tool from siblings like autoflow_status or autoflow_get_recent_assets.

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 provides clear contexts for use: inspecting progress, verifying visual output, and diagnosing UI state. It does not explicitly name alternative sibling tools or state when not to use it, but the use cases are sufficiently specific to guide an agent.

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