extract_image_exif

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

No annotations are supplied, so the description carries the full disclosure burden. It does disclose the output content (including a map link) and implies a read-only extraction, but says nothing about what happens when an image has no EXIF block, whether any authentication or rate limits apply, or whether remote fetching can fail — gaps that matter for a network-fetch tool.

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?

Two compact blocks — a one-line purpose statement followed by the argument — with the resource and returned fields front-loaded. The only mildly redundant element is the 'Recon Tool' label, and nothing else is padded.

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 extraction tool with an output schema (which covers return-value details), the description is nearly complete: purpose, output fields, and input format are all stated. The missing piece is failure behavior on images lacking EXIF, which would be useful but is not blocking.

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 0%, so the description must compensate for the single parameter, and it does: it specifies a direct HTTP/HTTPS URL and enumerates accepted file extensions (.jpg, .png, .tiff, .webp), which the schema does not. It stops short of noting whether redirects or non-image URLs are rejected.

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 names a specific verb and resource (extract EXIF/geotag from an online image) and enumerates exactly what is returned: camera make/model, creation timestamp, editing software, and GPS coordinates. That field list distinguishes it from siblings such as osint_geoint_lookup or scrape_url without requiring an agent to open another schema.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no sibling alternative is named. The only contextual hint is that the input must be a direct image URL, which is a precondition rather than a routing rule.

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