Paint: import an image

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

Annotations already declare the mutation/creation profile (readOnlyHint=false, idempotentHint=false), and the description usefully adds that the format is sniffed from raw bytes (png/jpg/bmp regardless of extension) and that the call either creates a canvas or appends a layer to an existing one. Missing is any note on overwrite/error behavior when the named canvas already exists, or how the `preview` reply interacts with the result, though the schema covers the latter.

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 dense sentences with zero filler. The primary intake decision is front-loaded, and the state-changing consequence (creates canvas vs adds layer) lands last as the closing clause.

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 5-parameter, 100%-documented, no-output-schema tool whose annotations cover the mutation profile, the description supplies exactly the missing runtime context: input mode selection, format sniffing, and create-vs-append outcome. Nothing an agent needs to invoke it correctly is absent.

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%, so baseline is 3, but the description genuinely adds semantic value: it explains the path-vs-data decision criterion and that declared extensions are not trusted (format sniffed from bytes), and it maps `canvas` to create-vs-append semantics. It leaves `preview` and `as_layer` entirely to the schema.

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?

States a specific verb and resource (importing a picture into the paint workspace) and is immediately distinguishable from reverse operations like paint_export by naming the two intake modes (`path` for files, `data` for held bytes). It stops short of drawing the boundary with closer siblings such as paint_layer or paint_canvas, which handle the same canvas/layer structure this tool also touches.

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?

Gives clear context for choosing between the two input modes: `path` for a file under the paint root, `data` with base64 when the agent already holds the bytes. It does not, however, name any alternative tool or state when not to use import (e.g. routing to paint_layer for in-memory composition), so it is clear context without exclusions.

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