Read photo metadata (EXIF)

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

Annotations already establish readOnlyHint/idempotent/local scope, but the description adds meaningful behavior beyond them: it flags privacy-sensitive fields, reports every metadata block with size, and discloses uneven format coverage (full for JPEG/PNG, EXIF-only via sharp for other formats). It stops short of describing the return structure or behavior when a photo has no metadata, which matters because there is no output schema.

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 lead sentence is front-loaded and the field enumeration earns its space by telling the agent what will be returned. The sentence is long and list-heavy, and the trailing web-version URL is of marginal use to an agent, but overall it is 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 one-parameter read-only tool with no output schema, the description covers inputs, output contents, format limitations, and privacy flagging well. What is missing is only edge behavior (no-metadata photos, error shapes), which is a minor gap rather than a blocker.

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?

There is a single parameter with 100% schema description coverage that already explains local path vs base64/data URI input. The description adds nothing about parameter formatting, which is acceptable given the schema does that job; baseline 3 applies.

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 specific verb+resource ('Show the hidden metadata in a photo') and then enumerates exactly what metadata it surfaces (camera make/model, lens, exposure, GPS, PNG text chunks, block listing). This is clearly a read/extraction tool and is distinguishable from the sibling image_exif_strip, which removes rather than reads metadata.

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 use case is implied clearly enough (inspect photo metadata), and the format-support sentence ('JPEG and PNG fully; WebP/AVIF/HEIC/TIFF EXIF via sharp') helps an agent decide applicability. However, there is no explicit when-to-use/when-not guidance and no routing to the obvious alternative, image_exif_strip, so the agent must infer the boundary itself.

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