ExifTool metadata

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds that it invokes ExifTool and reads local metadata, but it does not disclose potential behavior such as requiring ExifTool to be installed or failing on unsupported file types. This is acceptable given the annotations, but not richly transparent.

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 focused sentence that front-loads the action and resource, then adds concrete examples of the metadata categories. Every phrase earns its place with no repetition of schema fields or annotation values.

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 simple one-parameter, read-only tool with no output schema, the description gives enough context for an agent to invoke it correctly and understand what it will retrieve. A small gap is that it does not mention output format or failure modes, but these are not critical given the tool's simplicity and the safe-read annotations.

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 the only parameter, file_path, is already described as an absolute path to the photo, video, or document. The description reinforces this by mentioning local files but adds little semantic detail beyond the schema, so the baseline score of 3 is appropriate.

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 states a specific verb ('Read'), a clear resource ('metadata of a local photo, video or document'), and the method ('with ExifTool'). It also enumerates concrete metadata categories (GPS, camera, author, software, timestamps), making the tool's purpose immediately recognizable and distinct from the OSINT search siblings.

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 word 'local' clearly establishes that this tool is for on-disk files rather than online investigations, which implicitly differentiates it from the sibling tools (email, username, domain searches). However, it does not explicitly state when not to use it or name an alternative, so it stops short of full usage guidance.

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