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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false) and the description adds genuinely useful context: it is saved as a new revision that undo reverts, and it is atomic (if any part is refused, nothing changes), plus what gets skipped and returned in `skipped`. That is meaningful behavioral disclosure beyond the annotations. However, it does not cover permissions/auth requirements or rate limits, so it is solid but not fully transparent.

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?

It is front-loaded with the core action and grouped logically (what is imported, what is skipped, return/rollback, alternatives). It is dense but every sentence carries information; the only mild cost is the long single paragraph that compresses several concepts.

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?

Despite having no output schema and 8 parameters, the description covers import behavior, element handling, naming, skip list, return value ("the group and every layer made"), atomicity, and sibling selection. An agent has everything needed to call it correctly.

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 100%, so individual parameter documentation is already handled. The description adds semantics beyond the schema by explaining how `svg` markup is interpreted — each <g> becomes a group named from its id, data-name or inkscape:label — which tells the agent how to structure input for downstream select and animate.

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 — add an SVG as editable vector layers inside one new group — and enumerates what gets imported (paths, rectangles, circles, gradients, transforms). It also names the sibling it is not (shape_path) for exact geometric shapes, so an agent can distinguish it without opening either schema.

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?

Explicitly scopes usage: "Use it for artwork drawn elsewhere; for exact geometric shapes use shape_path," and redirects text and photos to create_layers and image layers. That gives when-to-use, when-not-to-use, and named alternatives in one pass.

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