create_canvas

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

With no annotations, the description carries the full burden, but it only says 'create a new,' implying non-destructive creation without explaining side effects, whether a new document/tab is opened, or whether an existing sprite is required. The word 'new' gives slight confidence of non-overwrite, but no real behavioral detail is disclosed.

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?

A single sentence containing no fluff communicates the core operation immediately. It is appropriately short for the simplicity of the tool, though it could afford a small amount of added context without becoming verbose.

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 three-parameter, no-annotation, no-output-schema tool, the description is thin. It omits behavior, parameter semantics, and return/output expectations, so an agent has to make assumptions about what 'create canvas' modifies and what it produces.

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 coverage is 0% and the description does not explain width, height, or filename. The Aseprite context makes it plausible they are pixel dimensions and a canvas name, but units, file implications, and relationships are left to inference.

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?

Describes a specific action (create) and resource (new Aseprite canvas), so an agent knows it instantiates a blank canvas rather than modifying an existing one. It does not explicitly contrast with siblings like resize_canvas or crop_canvas, but the verb and 'new' make the intended operation unambiguous.

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 when-to-use or when-not-to-use guidance is provided. The description does not mention alternatives or state prerequisites, leaving the agent to infer that this is for starting from scratch versus using resize_canvas or import_image_as_layer.

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