osint_exif_data

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

The description discloses behavioral traits beyond annotations: 'Pure local parse: read-only, non-destructive, deterministic, contacts no external service, rate-limited (5 requests/minute for anonymous callers).' This adds context about determinism, no external service calls, and rate limiting, which are not covered by the annotations.

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 well-structured and appropriately sized for the tool's complexity. It starts with a clear one-line summary, then expands on functionality, sibling distinctions, behavioral traits, and input constraints. Every sentence adds value without redundancy.

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?

Given the tool's complexity, the description covers all necessary aspects: purpose, input format and constraints, behavioral properties (read-only, deterministic, rate-limited), privacy features, and explicit sibling comparisons. The presence of an output schema and annotations complements the description, making it fully informative.

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 are no JSON parameters (0 params), and the schema is empty with 100% coverage. The description adds meaning by detailing the file input constraints: multipart/form-data, field 'image', max 10 MB, and supported image formats (JPEG, TIFF, PNG). This compensates for the lack of schema fields.

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 clearly states the tool as an 'EXIF Metadata Viewer' and enumerates specific functions: extracting EXIF, GPS, camera metadata, flagging privacy-sensitive content, and providing scrubbing recommendations. It explicitly distinguishes from sibling tools by naming alternatives like osint_email_headers, webdev_base64_image_encoder, and file_mime_type_lookup.

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 explicit guidance on when to use this tool (forensics/OSINT and pre-share privacy check) and when not to, naming specific alternative tools and their purposes. It also notes that EXIF is only present in JPEG/TIFF, setting expectations for input formats.

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