Edit image

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 that strip_metadata never re-encodes pixels (lossless), that remove_background triggers a one-time 4.4MB model download and always emits PNG, and what the tool returns. It does not say whether the source file is overwritten or how `out` defaults, which keeps it short of a 5.

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?

Four tight sentences, front-loaded with the operation taxonomy, then the highest-value caveats (lossless strip, model download, PNG output, return values). No 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?

No output schema exists, and the description compensates by describing the return values (real dimensions and byte size). Operations and key side effects are covered; minor gaps remain around overwrite behavior and how `out` interacts with the source path for an 8-parameter mutation tool.

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 63%, with the schema itself already documenting width, height, format, quality, and background. The description adds no parameter-level detail beyond restating the formats and the ops, so it neither compensates for the coverage gap nor exceeds the schema's baseline.

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?

Names the specific verb (edit) and enumerates all five operations (resize, compress, convert, strip_metadata, remove_background), with formats spelled out. This clearly separates it from the document/pdf siblings (doc_convert, pdf_edit) that share the editing domain.

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?

Usage is implied by the operation list, but there is no explicit when-to-use/when-not guidance, nor advice on choosing among the five ops (e.g. compress vs convert). With no competing image sibling, the routing need is lower, but the op-selection decision is left to inference.

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