Vectorize image

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

With annotations only covering safety hints, the description carries real weight: it discloses a 0.05 USDC charge on Base via x402, spending-limit checks, output dimension capping at 4096, and the 10-minute repeat-purchase short-circuit. These are exactly the non-obvious side effects an agent needs before invoking a paid, non-idempotent tool.

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?

Front-loaded with the core action and use case, followed by a compact input/output block — nearly every sentence carries new information. It is dense and slightly long, but nothing is redundant enough to cut.

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?

No output schema exists, yet the description names the return type (image/svg+xml), the delivery form (download link plus optional saved file), and the payment/size constraints. An agent can decide, pay, and handle the result without further discovery.

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 baseline is 3; the description adds the mutual-exclusion constraint ('Give exactly one of image_url or image_path') and input limits (8 MB, 8000 px) that the schema does not encode. That is genuine value beyond the per-parameter 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?

States a specific verb and resource ('Traces ... image into an SVG of filled paths') plus scope (colour count, format). It is clearly distinct from siblings like remove_background, optimize_image and image_palette, which do different transformations on the same input types.

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 an explicit fit statement — 'Best for logos, icons and flat artwork; a photo comes back as a stylised poster' — which tells the agent when the tool is appropriate and what quality to expect otherwise. It does not name which sibling to use instead for non-vector needs (e.g. optimize_image), so it falls short of a 5.

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