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

With no annotations, the description carries the full behavioral burden and does disclose two non-obvious traits: it is billed ('x402 price $0.01/call (USDC, eip155:8453)') and it is privacy-safe ('parsed in memory, never stored'). What it omits is failure behavior (JPEGs with stripped/no EXIF) and any input size or format limits, so the disclosure is good but not complete.

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 first sentence is strong and front-loaded with the output payload, but the third sentence ('Use this when an agent needs to camera, settings and GPS from a JPEG') duplicates the already-listed fields and is grammatically malformed, so it does not earn its place. The pricing sentence is dense but justified.

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 single-parameter tool with no output schema, the description usefully enumerates what comes back and discloses the payment requirement, which an agent must know before invoking. It stops short of covering error/no-EXIF behavior, which is the main remaining gap.

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 only one required parameter (imageBase64) and the schema already documents it at 100% coverage as 'JPEG (base64)'. The description's 'from a JPEG' restates this constraint without adding encoding, size, or format-expectation detail, so the 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?

States a specific verb ('Extract') and resource ('EXIF metadata from a JPEG') and enumerates the concrete fields returned (make/model, lens, exposure, timestamps, orientation, GPS as decimal lat/lon). No sibling tool overlaps this capability (media_color_convert and media_contrast_check operate on color/contrast, not metadata), so an agent can select it unambiguously.

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 implied context ('The OSINT-standard check for where a photo really came from', 'Use this when an agent needs to camera, settings and GPS from a JPEG') but the second clause is a broken restatement of the purpose and offers no alternatives or exclusions. There is no guidance on when NOT to use it, nor on what to use for non-EXIF image analysis or non-JPEG inputs.

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