Remove local image metadata

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

Goes well beyond the annotations: it discloses that the operation is lossless (no re-encoding), that it writes a new file rather than mutating the input (consistent with destructiveHint=false), that the output is re-inspected, and which metadata survives by default. What it omits is the reason for idempotentHint=false — e.g. whether an existing output_path is overwritten or rejected.

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 short sentences, each carrying a distinct payload: what it does, verification behavior, defaults, and output/non-goal. No filler and the core operation leads.

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 4-parameter write tool with no output schema, the description covers operation, formats, lossless guarantee, preservation defaults, output location, and the explicit non-goal of anonymizing visible content. The only residual gap is overwrite behavior on an existing output file, which is minor.

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 50% — the two boolean flags carry no schema descriptions — but the description compensates by stating that defaults preserve an orientation-only EXIF block and the ICC profile, which explains exactly what keep_orientation and keep_icc control. Path semantics are covered by the schema's own 'absolute local path, no URLs' text.

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?

A specific verb ("Remove") plus a precisely bounded resource ("metadata from JPEG, PNG, or WebP containers") plus a key qualifier ("without re-encoding image data"). The format restriction and the lossless framing make it unmistakable against siblings like abox_image_compress or abox_pdf_split.

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 context is implied rather than stated: 'Writes a new local file' and 'does not anonymize visible content' clarify scope but never name an alternative tool or a when-not condition. There is no guidance about prerequisites (does the output file need to not exist?) or what to do when metadata is unsupported.

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