image_convert

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

With no annotations, the description must carry the full behavioral burden, and it only lists transformation features. It never says whether output_path is overwritten, whether directories are created, what the tool returns, or how long the heavy pipeline (19 dither modes, Kuwahara, palette extraction) might take.

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 purpose is front-loaded in the first clause, which is good, but it then becomes a single run-on laundry list of every pipeline feature. For a 25-parameter tool some enumeration is warranted, yet the sentence is dense and hard to parse rather than structured.

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 complex 25-parameter, file-writing tool with no annotations and no output schema, the description explains the transformation broadly but omits return value, overwrite behavior, and how the preset parameter relates to the manual parameters. It is adequate but leaves real gaps.

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 56%, so the description should compensate. It does name most feature families (downsampling modes, palette sources, dithering, Kuwahara, tone controls, cleanup, outlines, grid), but it only restates the parameter names without adding syntax, ranges, or interactions beyond what the schema already documents.

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 — 'Converts an image to pixel art' — and names the concrete pipeline it uses. It never references any sibling tool (image_stylize_reel, palette_tool, image_detect_grid), so an agent can identify the function but must infer why to pick this over the adjacent image tools.

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?

There is no when-to-use, when-not-to-use, or alternative guidance at all. The mention of 'the full unified PixelForge pipeline' hints this is the comprehensive converter, but nothing tells the agent when to reach for it versus image_stylize_reel or a preset-only path.

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