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

The description discloses important behavioral details beyond the annotations: it decodes and re-encodes from raw pixels, drops specific metadata types, and has a 4 MP free-tier limit. Annotations indicate mutation is possible, and the description describes the write-copy behavior consistently without contradiction.

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 tightly written sentences convey the core behavior, the metadata dropped, and the free-tier constraint. Every sentence adds value, and the most important behavior is front-loaded.

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?

The description plus a fully documented input schema provide enough context for correct invocation. The out_path schema covers the download-link behavior, and the description explains the transformation. Minor gaps remain, such as behavior above the free tier, but these are not essential for basic use.

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 input schema already provides 100% coverage for all three parameters with clear descriptions. The tool description does not add parameter-specific semantics beyond the general purpose, so the baseline score of 3 is appropriate.

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 states a specific action: write a copy containing only pixels, dropping all metadata. It clearly differentiates this from sibling operations like image_compress, image_convert, or image_watermark by focusing exclusively on metadata 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 gives clear context for when to call this tool: when metadata such as EXIF, GPS, camera, and colour-profile data must be removed. It does not explicitly name alternatives or state when not to use it, but the intended use case is unambiguous.

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