batch_strip_gps_exif

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

No annotations are provided, so the description must fully describe behavior. It states it removes only GPS EXIF, implying no other EXIF is affected, but does not disclose whether files are modified in-place, what 'supported images' means, or any security/permission implications. This is insufficient for a tool with no 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 a single sentence, which is concise but overly brief. It fails to provide necessary structure or detail. While concise, it sacrifices completeness; every sentence should earn its place, but this one sentence is insufficient to cover even the basic usage.

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 complexity (8 parameters, 0% schema coverage, no annotations, many siblings), the description is severely lacking. It does not cover return values, side effects, or parameter usage. The agent would be unable to correctly invoke the tool without additional knowledge.

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%, meaning the description provides no information about the 8 parameters. The description does not mention folder_path, output_folder, recursive, or any other parameter. The agent receives no help beyond the raw schema, which is especially problematic for parameters like extensions or dry_run that need context.

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 removes GPS EXIF metadata from images in a folder. The verb 'remove' and resource 'GPS EXIF metadata' are specific, and the scope 'supported images in a folder' is clear. It distinguishes itself from sibling tools like batch_strip_exif (which removes all EXIF) and batch_strip_selected_exif_fields (which allows field selection).

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 lacks any guidance on when to use this tool versus its siblings. It does not mention prerequisites, conditions, or exclusions. For a tool with many siblings, this omission leaves the agent without decision criteria.

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