Convert image

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

No annotations are provided, so the description carries the burden. It discloses an important behavioral detail beyond the schema: transparency is preserved except for JPEG, where it is flattened onto the `background` color. This is concrete and useful, though it does not mention side effects like file overwriting or permissions.

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 sentences with no filler. The core conversion purpose is front-loaded, and the transparency caveat earns its place as a behavioral warning. Every word adds value.

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 plus schema covers the essential invocation details: input, output formats, optional output path, preview, quality, and background. The missing explicit sibling routing is a minor gap, but the tool is simple enough that an agent can invoke it correctly with the given information.

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 67%, and the description adds meaning to the under-documented `input` parameter by listing accepted source formats (GIF, TIFF, HEIC). It also clarifies the `background` parameter's role in JPEG flattening, which goes beyond the schema's simple 'CSS color' description.

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 specific verb ('convert') and resource ('image'), and immediately lists the target formats: jpeg, png, webp, avif. This clearly distinguishes it from siblings like crop_image, resize_image, and compress_image, even without naming them.

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 implies the tool is for format conversion and adds accepted input formats (GIF, TIFF, HEIC), but it does not explicitly say when to use this tool over alternatives such as compress_image. There is no when-not or exclusion guidance, so the agent must infer the appropriate use case.

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