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

With no annotations, the description carries the behavioral burden and does well: it explicitly says the image is not changed and lists the metadata categories returned, including hidden EXIF/GPS/colour-profile data and duplicate fingerprints. It does not cover error behavior, permissions, or whether remote URLs are fetched server-side, but the core non-mutating behavior is clear.

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?

It is a single front-loaded sentence with no filler. The enumerated facts are dense but each contributes useful scope, and the non-mutating constraint is stated first.

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 two-parameter read-only inspection tool with no output schema, the description does a good job of explaining what information is returned and that the source image is untouched. It lacks explicit alternative-routing guidance and some operational details, but the essential selection and invocation context is present.

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 description coverage is 100%, so the two input parameters are already well documented by the schema. The description does not add parameter-specific guidance, 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 resource (an image) and clearly scopes the operation to extracting facts without modifying it. It enumerates the kinds of facts returned and implicitly distinguishes itself from mutating siblings such as compress_image, convert_image, and remove_background.

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 phrase 'without changing it' implies this is the read-only inspection tool, which gives useful implied usage. However, it does not explicitly say when to choose this over siblings like extract_text or screenshot_url, nor does it state exclusions or prerequisites.

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