exiftool

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

No annotations are present, so the description must carry the full behavioral burden. It does disclose the key actions: reading, writing, editing, stripping, and modifying metadata, plus the output shape ('all metadata fields with their values'). However, it does not mention side effects like in-place file modification or failure behavior, which is a meaningful gap for a tool that can strip or alter metadata.

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 three sentences and front-loaded with the core function. The examples are useful but slightly repetitive with the opening, and the final 'strip or modify' clause partly overlaps with 'read, write, and edit'; still, it remains focused and efficient.

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 two-parameter tool with no output schema, the description covers the input (filepath), optional behavior via opts, supported file types, application examples, and output format. It could mention error cases or destructive-call warnings, but the core information needed to invoke the tool is present.

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%, with both filepath and opts already described. The description adds useful context for file types and the general purpose, but it does not materially extend parameter semantics beyond the schema. The opts example ('-all=') appears in the schema, so no new parameter-level information is provided by the description.

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 opens with a clear verb-resource pair ('Read, write, and edit metadata') and lists concrete file types and example uses like GPS extraction and author names, making the tool's purpose unmistakable. It also distinguishes exiftool from the security/network sibling tools by focusing on file metadata rather than scanning or exploitation.

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 gives strong contextual cues for when to use the tool: 'Use to extract hidden information' with realistic examples such as GPS coordinates and author names. It does not explicitly name alternatives or state when not to use it, but the examples and file-type list provide clear scope.

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