Edit local image EXIF tags

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

Goes well beyond the annotations by disclosing the post-write verification pass, that thumbnails and compressed picture payloads are retained, that non-targeted metadata survives, and the real risk that rebuilt EXIF can invalidate undocumented maker-note offsets. It also states the privacy property that values never enter arguments or results, which the annotations cannot express.

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?

Front-loaded with the core action and formats, then layers the verification and risk caveats. Sentences are dense and telegraphic ('Requires no browser', 'Values never enter tool arguments or results') but each carries distinct information, so little is wasted.

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?

With no output schema and a non-trivial binary rewrite, the description covers verification, retained blocks, residual metadata and known risk. It stops short of saying whether output_path may overwrite an existing file or whether the input is left untouched, which an agent would want before calling.

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 100% and each path parameter is already documented as an absolute local path with network shares refused. The description reinforces that edits_path is a bounded JSON file holding values rather than inline arguments, but adds little beyond what the schema already says.

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 pair (set/remove) and resource (EXIF tags) with supported formats (JPEG, PNG, WebP) and the edit mechanism (local JSON edits file). It implicitly separates itself from bulk-removal tools via 'Other metadata remains; this is not anonymization', but never names the exif_remove sibling that would be the actual alternative.

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: inputs must be local absolute paths, values must live in a companion edits file, and the operation is scoped to selected tags. The 'not anonymization' clause hints at a different tool but no sibling is named and no explicit when-to-use/when-not conditions are given.

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