vectorize_image

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

The description explains the output format (SVG) and response contents (path/URL and preview), providing basic behavioral insight. However, it omits details such as size limits, supported input formats, processing time, or any side effects. With no annotations, this is the sole source, so more would be helpful.

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 three sentences, efficient and front-loaded with the core action. However, it could be slightly tighter by merging the second and third sentences. Overall, no redundant information.

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?

The description lacks details like input format restrictions, size limits, or output quality expectations. Compared to similar tools, it does not differentiate its use case. Given the tool's simplicity (1 param, no output schema), additional context would make it more complete.

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 input schema already describes imageURI thoroughly (URL or file protocol). The description does not add any additional meaning or constraints beyond what the schema provides. Schema coverage is 100%, so baseline 3 is appropriate.

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 the tool vectorizes an image to SVG using Recraft. 'Vectorize' is a specific verb and the resource is an image. However, it does not distinguish from sibling tools like image_to_image or creative_upscale, which could cause ambiguity.

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?

No guidance is provided on when to use this tool over alternatives. It does not mention prerequisites, exclusions, or context for choosing vectorize_image over other image-processing tools. The agent receives no hints about appropriate usage scenarios.

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