strip_exif

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

With no annotations, the description explains key behaviors: output_path omission generates a sibling path, overwrite defaults to false, and optional dry-run, comparison, and report features. It could clarify if the original file is modified, but overall it is transparent enough.

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 two insightful sentences plus a brief third sentence. Every sentence adds value, and the purpose is immediately clear. No wasted words.

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 complexity (6 params, no annotations, but output schema exists), the description covers essential behaviors and optional features. It does not explain error conditions or return values, but the output schema fills that gap. Overall, it is sufficiently complete.

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?

Despite 0% schema description coverage, the description adds meaning for output_path, overwrite, dry_run, include_comparison, and write_report. Only image_path lacks explicit explanation, but it is self-explanatory. This compensates well for the schema gap.

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 verb 'Remove' and the resource 'EXIF metadata from a single image'. It distinguishes from sibling tools like batch_strip_exif by specifying 'single image', making the purpose unambiguous.

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 implies single-image use but does not explicitly state when to use this tool vs batch or field-specific alternatives. There is no exclusion guidance or mention of prerequisites.

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