strip-metadata

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

It discloses that stripping is lossless and removes specific metadata categories, which is useful. However, it does not state whether the operation modifies the original file or returns a new image, nor what happens for unsupported formats. With no annotations, this leaves key behavioral gaps.

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?

One compact sentence that conveys the action, scope, lossless nature, and supported formats. Every word adds information with no fluff.

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 mutation tool with no output schema and no annotations, the description should explain what the output is (e.g., whether it returns a stripped image or modifies in place). It is missing this critical context, making it incomplete for an agent to utilize correctly.

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?

The only parameter is 'image', but the description merely refers to 'an image' without explaining how to specify it (path, URL, base64, etc.). Schema coverage is 0%, so the description should compensate, but it does not add value beyond the schema.

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 action ('Remove all metadata') and specifies the metadata types (EXIF, GPS, XMP, ICC, IPTC) and supported formats (JPEG, PNG). This differentiates it from sibling read/edit tools by emphasizing complete removal.

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 use when stripping metadata from JPEG/PNG images, but does not explicitly state when to prefer this over siblings like edit-exif or when not to use (e.g., for selective metadata editing). No alternatives are named.

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