jpeg_exif_deep

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

No annotations provided, but the description effectively discloses behavioral traits: it returns deep EXIF data and flags forensic items. Assumes read-only operation.

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 sentences, front-loaded with purpose, no extraneous information.

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?

Lacks output format or structure description, which is needed since no output schema is provided. Otherwise covers inputs adequately.

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?

Only one parameter with 100% schema coverage; description does not add significant meaning beyond naming the file path, but it is consistent and adequate.

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?

Clearly states it performs deep EXIF analysis, listing specific components like GPS, timestamps, and forensic flags. Distinguishes from siblings such as img_metadata and jpeg_comment.

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?

Implies use for forensic deep EXIF analysis but lacks explicit guidance on when to use vs alternatives, or when not to use.

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