edit-exif

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It states that the tool edits fields and returns a modified image, but does not explain whether the original input is mutated in place, how existing metadata is handled, or whether the tool overwrites or preserves unspecified fields. It also omits any side effects or prerequisites (e.g., file permissions).

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 a single, concise sentence that directly states the tool's action and return value. There is no redundant or filler content; every word earns its place.

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?

Given the tool's complexity (4 parameters, nested objects, no annotations, no output schema), the description is too sparse. It fails to mention the required 'image' parameter, how to provide the image (path/url/base64/buffer), the existence of 'clearGps', or the meaning of the various EXIF fields. The agent would need to rely entirely on the schema without additional guidance.

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%, and the description does not compensate. It mentions 'EXIF and GPS fields' but does not map this to the specific 'fields', 'gps', or 'clearGps' parameters. The schema provides structure (e.g., image kind, field names) but the description adds no explanation of how to use these parameters, their formats, or relationships.

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 uses a specific verb ('Edit') and identifies the resource ('EXIF and GPS fields in a JPEG image'). It clearly distinguishes from the sibling read-only tools like read-exif and read-metadata by indicating a modification operation. The return format (base64 data URL) is also stated, making the purpose unambiguous.

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?

The description clearly states the tool's purpose, which is to edit EXIF and GPS fields. It doesn't explicitly mention alternatives or exclusions, but the sibling tool names (read-exif, strip-metadata, etc.) make it obvious when this tool should be used versus read-only or stripping tools. The context is clear enough for an agent to decide.

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