Convert local HEIC photos

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

Adds substantial context beyond the annotations: metadata is stripped, output is 8-bit SDR, JPEG/WebP are lossy, a local browser is required, and the tool pre-validates extents/dimensions and compares every output pixel post-decode. The destructiveHint=false annotation is consistent with writing only to a new directory, and the description explains the data-loss behaviors (metadata omission) that annotations cannot express.

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?

Front-loaded with the action and output, then layered with validation and caveat details. Dense and jargon-heavy ("admitted", "reference budgets") but each sentence carries distinct information; only the validation-procedure sentence borders on over-detail for a tool description.

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?

No output schema exists, and the description never states what the result looks like (counts, paths, per-file verification report) despite describing a verification step. Otherwise it covers format, quality implications, environment requirements, and data-loss caveats adequately for a 4-parameter tool.

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 only 50%: input_path and output_dir are documented in the schema, but format and quality are not. The description mentions JPEG/PNG/WebP formats (mapping loosely to format) but says nothing about quality semantics or defaults above the schema's own default 0.92, so it does not compensate for the gap.

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 (convert) and resource (HEIC images, including tiled grids) with the destination artifact (a new directory of JPEG/PNG/WebP). It is clearly not abox_image_convert or abox_avif_convert by virtue of the HEIC/HEVC scope, though it never names those siblings 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?

"Requires a local browser" and "offline" imply the execution context, but the description never says when to prefer this over abox_image_convert or abox_avif_convert, nor when not to use it. Usage is inferable, not stated.

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