Export a SOP's geometry as SVG

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

The description discloses key behaviors beyond annotations: projects to x/y (drops z), auto-fits viewBox, supports stroke/fill/scale/flip_y, writes to disk when output_path supplied, always returns SVG string. No contradiction with annotations (readOnlyHint=false, destructiveHint=true, openWorldHint=true).

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 concise (4 sentences) and front-loaded with the key action and resource. Each sentence adds value without redundancy. Structure is clear and efficient.

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?

Given the tool has 7 parameters and complex behavior (SVG generation, file output), the description is mostly complete. It covers input, process, output format, and file writing. Missing details like coordinate system origin or error handling, but overall adequate.

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 some semantic context (e.g., 'each primitive becomes one <polyline>', 'auto-fits viewBox'), but most parameter meanings are already well-defined in the schema. No significant additional insight beyond what the schema provides.

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 it exports SOP geometry to SVG, detailing the process (walk primitives, emit polylines) and use cases (pen-plotter, laser, print). The tool name is self-explanatory, and the description adds specific context that distinguishes it from siblings (e.g., no other export SVG tool listed).

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 provides context on when to use the tool (for vector output like pen-plotter/laser/print) but does not explicitly state when not to use it or mention alternatives. While the use cases are clear, the lack of explicit exclusions lowers the score slightly.

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