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

With no annotations, the description carries the full burden and does well: it discloses the Pro-plan requirement, that dry_run computes sizes without processing, and that results come back as a one-hour download URL plus a per-step report. It does not cover failure/partial-failure behavior or any cost/rate-limit implications.

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?

Dense but front-loaded, leading with the core purpose before schema detail. The pipeline/ops enumeration is necessarily long, though the parenthetical nesting makes it slightly harder to scan than a bulleted form would.

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 7-param tool with a nested object and no output schema, the description covers the return value and the two alternative input modes (pipeline vs preset). Minor gaps remain on how version/name interact and on step-failure handling.

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?

Far exceeds the 71% schema coverage by documenting the nested pipeline shape (steps with op/params/when), enumerating all ops, listing the allowed 'when' conditions, and naming the available presets and templates. It also clarifies that dry_run previews rather than processes.

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 ('run a multi-step workflow on an image in one call') and immediately supplies concrete op examples. It is clearly differentiated from single-op siblings like compress_image, convert_image, and remove_background, which this tool composes.

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?

Gives a clear context for use ('one call' doing background removal, resize, convert, compress), a Pro-plan prerequisite, and a dry_run mode for previewing. It never explicitly says to prefer this over chaining the individual sibling tools, so the alternative routing is implied rather than stated.

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