export_page_png

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does disclose the key behavior that the image is returned to the agent, and it explains the path default behavior. However, it does not mention whether the operation is read-only, what happens if the page does not exist, or whether a file is also written to disk when path is provided.

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 and well-structured. The purpose and usage guidance are front-loaded in the first two sentences, followed by a compact parameter breakdown. No unnecessary words or redundant details are present.

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 two optional parameters and no output schema, the description covers the core behavior, the returned image, parameter defaults, and the intended workflow context. A minor gap is the lack of detail about error behavior or the exact relationship between the output file and the returned image, but overall it is sufficient for an agent to call it 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 0%, so the description must compensate, and it does. It explains both parameters: path is the output .png path with an auto-named temp file fallback, and page defaults to the active page. This fully clarifies the parameter semantics beyond the bare schema.

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 exports a page as PNG and returns the image for visual inspection. This distinguishes it from other sibling tools like auto_layout, drop_shape, or get_page_state, which perform different actions. The purpose is specific and actionable.

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 explicitly says to use this tool after dropping/connecting/layout operations to verify results and iterate. This gives clear contextual guidance, though it does not mention when not to use it or suggest alternative tools for other export or inspection needs.

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