Screenshot the Flow tab

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

The description discloses the key behavior: it saves a PNG file and returns its absolute path. Annotations already indicate the operation is read-only, idempotent, and non-destructive, so the description adds useful file-output context without contradicting the annotations.

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 short sentences with no filler. The primary behavior is front-loaded, and the second sentence justifies the tool's usefulness without repeating the schema or title.

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 zero required parameters, full schema coverage, an output schema, and comprehensive annotations, the description provides enough operational context. It states what happens, what is returned, and why an agent would use it.

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?

Input schema coverage is 100%, with both 'label' and 'full_page' already described in the schema. The tool description does not need to add parameter meaning, so the baseline score of 3 applies.

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 action ('Save a PNG of the tab this server owns') and its result ('return its absolute path'). It clearly identifies the target resource as the screenshot of the Flow tab, and no sibling tool performs the same function, so differentiation is implicit.

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 offers a clear use case: 'Useful to see what the agent or Scene Builder is showing.' It does not explicitly state when not to use it or name alternatives, but the context is sufficient for a tool with no overlapping screenshot sibling.

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