art.canvas.save

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that a PNG file is written, but it does not describe whether an existing file is overwritten, whether the canvas is mutated in memory, whether the operation is safe to repeat, or what happens when the session_id is invalid.

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 a single, front-loaded sentence with no filler. For a simple two-parameter tool, this is appropriately concise.

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?

The description is minimal but viable given that the schema covers both parameters and the tool is a simple save operation. Still, with no output schema and no annotations, return behavior, overwrite semantics, and failure cases are left unspecified.

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?

Parameter coverage is 100%, so the schema already documents session_id and output_path, including the default path. The description adds nothing meaningful beyond the schema for parameter semantics.

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 verb and resource: 'Save the current canvas to a PNG file.' It clearly distinguishes this from sibling canvas tools like art.canvas.create, art.canvas.draw_rect, and art.canvas.get_state, which concern editing or querying rather than persisting.

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 intended usage is reasonably implied: use this when you want to persist the current canvas to a PNG. However, it does not explicitly state when not to use it, mention prerequisites like an initialized session, or contrast it with alternative tools.

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