ps_save_as_png

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action and that path is optional, but it does not explain what happens when path is omitted, whether an existing file is overwritten, or whether a save dialog is shown. This leaves a significant ambiguity for a save/export operation.

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 short, front-loaded sentence that conveys the core action and parameter status without redundancy. Every word 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 one-parameter export tool, the description is mostly adequate, but the optional path behavior is unexplained. A caller cannot tell whether omitting path triggers a dialog, defaults to a location, or fails, which is a meaningful gap. No output schema exists, but the description still should clarify the default behavior.

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 100% and both the schema and description document the 'path' parameter and its optionality. The description adds no extra meaning beyond the schema, such as default save location, required extension behavior, or what omitting the path does, so the baseline score of 3 is appropriate.

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 action: export the current Photoshop document as a PNG image. It names the specific verb, resource, and output format, which distinguishes it from sibling tools like ps_save_as_psd and ps_save_as_jpg.

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?

No guidance is given on when to use this tool instead of ps_save_as_psd, ps_save_as_jpg, or ai_export_png. The phrase 'current Photoshop document' implies the tool applies to Photoshop only, but no exclusions, conditions, or alternatives are mentioned.

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