forensics_exiftool

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the ability to read/write metadata, but fails to mention potential side effects of writing, such as altering file integrity, or what output to expect. This is insufficient for a tool that can modify files.

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 sentence of six words, front-loaded with the essential verb and resource. It is extremely concise with no wasted words, and every word contributes to the meaning.

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?

The tool is relatively simple with two parameters, but the description is too terse to be complete. It does not explain parameter semantics, output format, or any caveats about modifying metadata. Given no output schema or annotations, the description should provide more context to be fully useful.

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?

The schema has 0% description coverage, and the description does not explain the 'file' or 'additional_args' parameters. 'additional_args' likely means extra exiftool arguments, but this is not stated, leaving users to guess. The description adds no meaning beyond the schema.

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 'Read/write file metadata with exiftool' clearly states the tool's function with a specific verb (read/write), resource (file metadata), and tool (exiftool). This distinguishes it from sibling forensics tools like binwalk, steghide, and strings which have different purposes.

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 usage context is implied by the description—use when you need to inspect or modify file metadata. However, there is no explicit guidance on when to avoid this tool or mention of alternatives, which would be clearer.

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