process_image

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

With no annotations provided, the description carries the burden of behavioral disclosure. It adds meaningful details: single-pass processing, one-time JPEG re-encoding, and that optional spec arguments are validated against the final result and reported under `spec`. It does not cover failure modes or input format restrictions, but the core execution behavior is transparent.

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 tightly structured: a one-sentence purpose, a concrete operations example, a concise list of available ops, and two short paragraphs explaining the pipeline benefit and spec-checking behavior. Every sentence earns its place, and the core purpose is front-loaded.

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 10-parameter tool with no annotations and zero schema descriptions, the description is not fully complete. It covers the central `operations` parameter and the pipeline concept well, but it leaves the optional spec arguments and other tuning parameters under-specified, which an agent would need to invoke the tool correctly for advanced use.

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 compensate. It does a good job on `operations`, showing a full JSON example and listing valid op names, and it alludes to 'spec arguments'. However, it does not explain other parameters such as `quality`, `backend`, `max_width`, `min_width`, `max_height`, `min_height`, or `orientation`, leaving significant semantic gaps.

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 opens with a clear verb and resource: 'Apply a custom sequence of operations in one pass.' It explicitly lists the available operations, which map directly to the sibling individual-operation tools, so an agent can tell that this is the composite/pipeline counterpart to crop_image, resize_image, adjust_image, etc.

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?

It gives a concrete reason to choose this tool over chaining siblings: running operations as one pipeline re-encodes the JPEG only once and avoids stacking compression artifacts. It does not explicitly state when to prefer a single-operation sibling, but the 'custom sequence' framing and op list make the intended usage clear.

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