search_exif

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

No annotations are provided, so the description bears full responsibility. It discloses that it uses exiftool, is passive/public-source, and flags GPS location. However, it does not mention whether it modifies the file or any side effects, which is acceptable given the read-only nature implied by 'passive'.

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 two sentences long with an additional authorization sentence. It front-loads the core action and avoids redundancy. Every sentence adds value.

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?

Without an output schema, the description should detail the return format. It lists some metadata fields but does not specify whether output is always JSON or text, or how errors are handled. The presence of a json_output parameter suggests configurable output, which is not explained.

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 50% (only json_output has a description). The description clarifies that the 'file' parameter is a local file path, adding value beyond the schema. However, it does not explain the json_output parameter beyond what the schema already says, leaving the default output format unmentioned.

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 explicitly states the tool extracts embedded metadata (EXIF/IPTC/XMP) from a local file using exiftool, listing specific fields like camera make/model, GPS coordinates. This clearly distinguishes it from sibling tools that search online or perform other operations.

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 provides clear authorization guidelines: 'Authorized use only: your own assets or a target you are authorized to assess.' It does not explicitly compare to alternatives, but the local file focus inherently differentiates it from sibling tools. No when-not-to-use or exclusions are stated.

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