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

Annotations declare a non-read-only, non-destructive, non-idempotent operation, and the description goes beyond that by disclosing the asynchronous contract: it returns a toolExecutionId and results must be fetched via get_tool_execution as an SVG fileId plus downloadUrl. It stops short of noting whether the source file is retained or any rate/size constraints, but the async behavior is the key trait an agent needs.

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?

Two tight sentences with zero filler; the output/pipeline information is front-loaded immediately after the purpose so the agent learns it is async before invoking. Every clause carries 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?

For a one-parameter tool with an output schema, the description covers the essential async lifecycle and naming of the follow-up tool. It omits any constraints on acceptable input images (allowed formats, resolution limits) that would matter before committing to a long-running job.

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?

There is a single parameter with 100% schema description coverage, and the schema already explains that imageFileId comes from upload_file, list_files, or a succeeded image-generation result. The description adds no format, size, or validity constraints beyond that, so the baseline of 3 applies.

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+resource pair ('Create an SVG vector version of an existing raster image') that is unmistakably distinct from neighbors like upscale_image, remove_image_background, and generate_image. An agent can tell exactly what it produces (SVG) and what it consumes (a raster image file) without opening the schema.

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 names the companion tools (get_tool_execution) but never states when to choose vectorize_image over related transforms such as upscale_image or remove_image_background, nor any preconditions. Usage is implied by the purpose rather than explicitly guided.

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