Convert image format

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

With annotations covering the safety profile, the description still adds substantial behavior: transparency handling (background for JPEG, or always with flatten), EXIF rotation applied, SVG rasterisation sizing rules and the fact that scripts never run, plus hard scaling limits at 16384 px/side and 100 MP. These are non-obvious side effects an agent could not infer from annotations or schema.

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 front-loaded with the primary action, then proceeds in tight clauses covering inputs, edge cases and limits — nearly every sentence carries actionable information. The trailing web-version URL is the one element that does not help an agent call the tool.

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 7-parameter mutation of files with no output schema, the description covers input handling, edge cases, safety limits and the SVG path thoroughly. The remaining gap is what the result contains (written path vs. base64 payload), which is only inferable from the `returnBase64` schema entry.

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 the baseline is 3, but the description adds real meaning by explaining the interaction between parameters: transparency is filled with `background` only for JPEG unless `flatten` is on, which is not stated in either parameter's own text. It also ties the SVG output size rule to the input rather than to a parameter.

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 opening sentence states a specific verb and resource and enumerates every supported output format (PNG, JPEG, WebP, AVIF, GIF, TIFF), so an agent knows exactly what the tool does. It does not differentiate from the overlapping sibling image_svg_to_png, which also produces a raster from an SVG — the one gap keeping it below a 5.

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?

Usage is implied: convert an image when a different output format is needed, with input formats listed so an agent can judge applicability. But there is no explicit when-to-use/when-not statement and no named alternative (e.g. image_svg_to_png, image_compress, image_resize) to route between similar tools.

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