ai_export_png

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

No annotations are provided, so the description carries the behavioral burden. It does add meaning by disclosing the transparent background and the current-document scope. However, it omits what happens when path is omitted, whether existing files are overwritten, and any return or error behavior.

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?

Two short sentences with no filler. The essential facts—current document, PNG format, transparent background, and optional path—are stated clearly and front-loaded.

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?

With no output schema and no annotations, the description is thinner than it should be. It does not explain the default export location or filename when path is omitted, and it does not help the agent choose between this tool and sibling export/save tools.

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 input schema already covers path, noting that it is optional and should include the .png suffix, which is 100% coverage. The description merely repeats that path is optional and adds no additional parameter-level meaning.

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 the exact operation: export the current Illustrator document as a PNG bitmap, and adds the useful detail of a transparent background. This clearly distinguishes it from vector export via ai_export_svg and Photoshop-based PNG export via ps_save_as_png.

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?

There is no guidance about when to use this tool instead of ps_save_as_png, ai_export_svg, or ai_save_as_ai. It only scopes the operation to the current Illustrator document, which is more about purpose than usage conditions.

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