pixelart_create_canvas

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

The description discloses that the tool creates a new canvas (mutation) and returns a JSON confirmation, which aligns with the annotation readOnlyHint=false. It does not mention potential side effects, error cases (e.g., if canvas_id already exists), or resource limits. The description adds some behavioral context beyond annotations (return format) but omits important edge-case 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?

The description is short with a clear purpose statement upfront, followed by a bullet-like list of args and returns. It is not verbose and communicates essential information efficiently. Minor redundancy in repeating parameter names does not significantly detract.

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 specifies the canvas's purpose (single tile/sprite) and notes the return format (JSON string with canvas_id, width, height). It does not cover error handling, but given the tool's simplicity and the presence of an output schema, the description is largely complete for typical usage. Missing details like duplicate handling slightly reduce completeness.

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 provides detailed descriptions for all four parameters (width, height, canvas_id, background), including constraints and defaults. The description merely repeats the parameter names ('canvas_id, width, height, background RGBA') without adding new meaning. Since schema coverage is effectively 100%, the description adds no additional semantic value.

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 creates a new blank pixel-art canvas and specifies it's for a single tile/sprite surface. This distinguishes it from sibling tools like pixelart_create_tileset (which creates a collection) and pixelart_import_canvas (import from external). The verb 'create' and resource 'canvas' are specific and 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?

The description implicitly guides usage by stating it creates a blank canvas for sprites, which helps an agent decide when to use it (e.g., to start a new canvas). However, it does not explicitly mention when not to use it or provide alternatives like using pixelart_import_canvas for importing existing images. The context is clear but lacks exclusions.

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