image_transform

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals operation ordering, default output path (~/Downloads/openmedia/), that the result is written to disk, that rotate expands canvas, and that return_preview optionally returns a preview to the model. It does not detail error handling or file overwrite behavior, but the key behavioral traits are covered for a safe default. Slight gap on edge cases but overall strong.

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 well-structured and front-loaded with the operation order and key behavior. It uses a clear Args list for parameters, avoiding prose. Each sentence earns its place: the intro states purpose, the next explains order and application, then the Args block covers all parameters with concise definitions. No redundancy or filler.

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?

Given the complexity (11 parameters, no schema descriptions, no annotations, no output schema), the description is remarkably complete. It explains every parameter's meaning, defaults, operation order, default output path, and optional preview. The only minor omissions are error handling and file overwrite policy, but these are not essential for a basic agent to invoke the tool correctly. The description provides everything needed for correct usage.

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 description coverage is 0%, so the description must explain all 11 parameters, and it does. Each parameter (source, output_path, resize_width, resize_height, crop, rotate, flip, grayscale, output_format, quality, return_preview) has a clear meaning, including units, defaults, and allowed values (e.g., crop format, flip options). This fully compensates for the lack of schema descriptions.

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 explicitly states the tool transforms images with a list of operations: crop, resize, rotate, flip, grayscale, and format conversion. It makes the resource (image) and action (transform) clear, distinguishing it from other media tools like audio_convert or video_clip. The operation order is even specified, leaving no ambiguity about what the tool does.

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 usage context by listing image-specific transformations and noting that only specified operations apply. It doesn't explicitly name alternatives or when not to use it, but sibling tools are clearly for different media (audio/video) or separate purposes (image_info, image_view), making misselection unlikely. Clear context but no explicit exclusions, so a 4 is appropriate.

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