Inspect local image metadata

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

Annotations already cover readOnly, idempotent, non-destructive and closed-world, so the bar is lower. The description still adds real value by disclosing the output scope: presence and counts of supported blocks, with private tag values and image bytes withheld — information an agent cannot get from the 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?

Two tight sentences with the non-modifying guarantee and supported formats front-loaded, followed by the report scope. No filler.

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?

With no output schema, the description carries the burden of describing returns, and it does so at a high level (presence and counts, values withheld). It does not enumerate which metadata blocks are 'supported', leaving some ambiguity, but nothing critical for correct invocation is missing.

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 100% and the single input_path parameter is fully documented in the schema, including the refusal of URLs and network shares. The description adds nothing parameter-specific, so the baseline 3 applies.

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?

States a specific verb and resource ('Read the metadata inventory') and narrows the scope to local JPEG, PNG or WebP files. The 'without modifying it' clause and 'presence and counts' framing clearly separate inspection from siblings like abox_exif_edit or abox_exif_remove, though no sibling is named explicitly.

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?

Usage is implied by 'inspect' and the read-only framing, but it never says when to choose this over abox_exif_edit, abox_exif_remove, abox_gif_inspect or abox_file_hash. No exclusions or prerequisites are stated beyond the format list.

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