import_open_design

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

With no annotations, the description carries the burden of disclosing side effects. It reveals conversion scope (shapes, tokens, loss report) and warns about writing, but does not describe what happens on write (overwrite, merge, permissions) or any other side effects beyond the dryRun preview.

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 two sentences: the first states purpose and scope, the second gives a specific usage recommendation. Information is front-loaded and every sentence earns its place without filler.

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 tool with no output schema, the description explains inputs, conversion behavior, and return value (loss report). It lacks explicit return-value structure, but the loss report mention and dryRun guidance are sufficient for a complex import tool with five parameters.

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 the baseline is 3. The description adds minimal extra parameter context: it clarifies the bundle format (manifest.json + SVG + tokens.css) but does not significantly extend understanding beyond the schema's per-property descriptions.

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 a specific action ('Import an Open Design handoff bundle') with a defined resource ('into a Penpot file') and enumerates concrete conversion behaviors (SVG shapes, CSS custom properties, tokens, loss report). This differentiates it from sibling import_figma by naming the Open Design format.

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?

It explicitly instructs to use dryRun=true first for preview, which is a clear usage guideline and implies the alternative of executing the import. It does not explicitly exclude alternative tools, but provides enough context about the intended workflow.

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