Trace a local image into SVG

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

Beyond the annotations, the description discloses that the trace is a lossy shape interpretation, that complex traces are refused, that it writes and verifies a static path-only SVG, and that it requires a local browser. It does not discuss overwrite behavior for an existing output_path or expected runtime, so it stops short of full behavioral coverage.

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 four compact sentences, front-loads the core action and output, then adds suitability and constraints. There is no repetition or 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 an eight-parameter local file conversion tool with no output schema, the description gives a clear output artifact and key behavioral constraints. It is not fully complete because it omits semantics for min_area and corner_angle and does not state what happens if output_path already exists.

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 description adds meaning for several parameters by mentioning automatic or explicit threshold, inversion, detail, and single-color output. However, schema description coverage is only 25% and the description does not explain fill format, min_area, or corner_angle, leaving several parameters underspecified.

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 states a precise verb and resource: trace a still JPEG, PNG or WebP into a single-color SVG path. It names the three raster formats and the output artifact, which clearly separates it from siblings such as abox_svg_to_image and abox_image_convert.

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 says the tool is 'best suited to logos and line art' and refuses overly complex traces, giving real suitability guidance. It does not explicitly name an alternative tool for photographic or non-line-art inputs, so a sibling-level routing rule is missing.

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