image_process

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

No annotations are provided, so the description must carry the behavioral burden. It discloses pricing (1 cent) and lists operations, but omits critical behaviors such as the default metadata stripping (implied by keep_metadata default false but not stated), output handling, destructive nature, or any authentication requirements. This is a serious gap for a mutation tool.

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 a single sentence that efficiently lists all operations and the cost, with the key information front-loaded. There is zero wasted text, and it is well-structured for quick scanning.

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 tool with 14 parameters, nested objects, and no annotations, this description is severely under-specified. It omits the required 'file' parameter, output_path behavior, defaults for fit/quality/watermark options, and any return format. The agent would struggle to use this tool correctly without additional external knowledge.

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?

With only 14% schema coverage, the description must compensate for undocumented parameters. It enumerates operations but does not map them to specific parameters (e.g., 'resize' to resize_width/height and fit, 'compress' to quality). It provides a high-level overview but fails to explain parameter semantics like the 'fit' enum or 'rotate' auto mode, leaving too much to inference.

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 clearly states the tool performs image manipulations (resize, crop, rotate, convert, compress, strip EXIF, watermark) in one call. This distinguishes it from PDF tools and image_info (which likely only reads metadata), but it does not explicitly differentiate from image_info or other image-related tools, so a 4 rather than 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?

There is no guidance on when to use this tool versus alternatives. The only hint is 'in one call', suggesting combined operations, but no explicit use cases or exclusions (e.g., 'use image_info for metadata-only tasks'). An agent has to infer usage from the operation list.

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